You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2020/05/05 19:20:00 UTC
[jira] [Resolved] (SOLR-14425) Fix ZK sync usage to be synchronous
(blocking)
[ https://issues.apache.org/jira/browse/SOLR-14425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley resolved SOLR-14425.
---------------------------------
Resolution: Not A Problem
Not actually a problem; it was my misunderstanding.
> Fix ZK sync usage to be synchronous (blocking)
> ----------------------------------------------
>
> Key: SOLR-14425
> URL: https://issues.apache.org/jira/browse/SOLR-14425
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: David Smiley
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As of this writing, we only use one call to ZK's "sync" method. It's related to collection aliases -- I added this. I discovered I misunderstood the semantics of the API; it syncs in the background and thus returns immediately. Looking at ZK's sync CLI command and Curator both made me realize my folly. I'm considering this only a "minor" issue because I'm not sure I've seen a bug from this; or maybe I did in spooky test failures over a year ago -- I'm not sure. And we don't use this pervasively (yet).
> It occurred to me that if Solr embraced the Curator framework abstraction over ZooKeeper, I would not have fallen into that trap. I'll file a separate issue for that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org