[
https://issues.apache.org/jira/browse/SOLR-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697552#comment-14697552
]
Scott Blum edited comment on SOLR-6629 at 8/14/15 6:58 PM:
-----------------------------------------------------------
Second pass, I think this is actually in a good state (ALL TESTS PASSING). We
do need to chat through the new handling of lazyCollections some more, but I
thought I would present to you a working version in code of what I was talking
about.
We should also consider optimizing lazyCollectionState to do temporary caching
(cache for 2 seconds?) to avoid hitting ZK rapidly in succession.
was (Author: dragonsinth):
Second pass, I think this is actually in a good state. We do need to chat
through the new handling of lazyCollections some more, but I thought I would
present to you a working version in code of what I was talking about.
We should also consider optimizing lazyCollectionState to do temporary caching
(cache for 2 seconds?) to avoid hitting ZK rapidly in succession.
> Watch /collections zk node on all nodes
> ---------------------------------------
>
> Key: SOLR-6629
> URL: https://issues.apache.org/jira/browse/SOLR-6629
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Noble Paul
> Fix For: Trunk
>
> Attachments: SOLR-6629.patch
>
>
> The main clusterstate.json is refreshed/used as a poor substitute for
> informing all nodes about new or deleted collections even when the collection
> being created or deleted has state format > 1. When we move away from state
> format 1 then we should do away with this workaround and start watching the
> /collections zk node on all nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
