[
https://issues.apache.org/jira/browse/SOLR-8323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277927#comment-15277927
]
ASF GitHub Bot commented on SOLR-8323:
--------------------------------------
Github user romseygeek commented on the pull request:
https://github.com/apache/lucene-solr/pull/32#issuecomment-218122269
New plan! We now have a separate notification thread, and change
notifications are placed into a LinkedBlockingQueue that the thread waits on.
A caveat: the queue is currently unbounded, which is a Bad Thing. I'm not
sure of the best way forward here - make it bounded, and just drop
notifications if the queue is full? Make a note on the collection predicate
javadocs that all predicates run in a single thread, and users need to be
careful not to run slow code in them?
> Add CollectionWatcher API to ZkStateReader
> ------------------------------------------
>
> Key: SOLR-8323
> URL: https://issues.apache.org/jira/browse/SOLR-8323
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 6.0
> 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: [email protected]
For additional commands, e-mail: [email protected]
