[
https://issues.apache.org/jira/browse/SOLR-8323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273176#comment-15273176
]
ASF GitHub Bot commented on SOLR-8323:
--------------------------------------
Github user markrmiller commented on the pull request:
https://github.com/apache/lucene-solr/pull/32#issuecomment-217291207
> Although, thinking more about that, we already have a separate executor
for watchers, don't we?
Yes, every watch firing event should run from a dedicated executor rather
than using ZK's event thread. I have not dug in enough here to know it covers
what you guys are talking about, but holding up a Watcher thread should no
longer interfere with ZK clients internal event thread.
> Add CollectionWatcher API to ZkStateReader
> ------------------------------------------
>
> Key: SOLR-8323
> URL: https://issues.apache.org/jira/browse/SOLR-8323
> Project: Solr
> Issue Type: Improvement
> Affects Versions: master
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Attachments: SOLR-8323.patch, SOLR-8323.patch, SOLR-8323.patch,
> SOLR-8323.patch
>
>
> An API to watch for changes to collection state would be a generally useful
> thing, both internally and for client use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
