[
https://issues.apache.org/jira/browse/SOLR-6571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152232#comment-14152232
]
Mark Miller commented on SOLR-6571:
-----------------------------------
One of my favorite subtleties was that some Watcher events don't require that
you re-create the Watcher. That's a bid insidious given the API ;)
> Need a znode watcher support class
> ----------------------------------
>
> Key: SOLR-6571
> URL: https://issues.apache.org/jira/browse/SOLR-6571
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Timothy Potter
>
> When implementing SOLR-6249, [~noble.paul] points out that
> ZkIndexSchemaReader doesn't watch the managed schema znode correctly and
> should use a strategy similar to what ZkStateReader does so that watchers
> persist across zk client connection failures:
> The correct example is the constructor of ZkStateReader
> zkClient = new SolrZkClient(zkServerAddress, zkClientTimeout,
> zkClientConnectTimeout,
> // on reconnect, reload cloud info
> new OnReconnect() {
> //implement stuff here
> }
> });
> this ensures that the watchers are persisted across reconnect.
> We need a watch support class to help developers implement watchers correctly
> instead of having some code do it correctly and other code not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
