[
https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052890#comment-14052890
]
Noble Paul commented on SOLR-5473:
----------------------------------
bq. I don’t doubt we can come to agreement on how to handle the API.
I know . We just need a few iterations.
bq.I want to talk about cached clusterstate and watchers. Because, apparently,
that is really what this issue is
I'm glad that we are discussing this. This is the meat of the issue . And it is
EXTREMELY IMPORTANT that YOU agree with this aspect of the issue and all the
changes involved in that
bq.If you are monitoring a cluster of many collections in the Solr admin UI and
nodes die and take out collections that are not hosted on the admin UI node,
when will you see this reflected by the cloud visualization tab?
All changes will be visible realtime. The point is nodes NEVER cache any states
(only Solrj does SOLR-5474). .nodes watch collections where it is a member.
Other states are always fetched just in time from ZK.
bq.Also, if we are going to move to this different core way of doing things, do
we yet fully understand all of the changes and implications,
Yes , the changes are quite simple
# Nodes will only watch collections where it is a member of
#* when a core is registered, add a watch for that collection (don't add
duplicates )
#* When a core is unregistered, remove the watch . (only if no other core
needs that collection)
# Don't watch anything else
# Hit ZK for any data that is not watched realtime
bq.And can we change the title of this issue to reflect it’s full scope?
I shall do it
I am glad to add more tests . We can open tickets and and target them one by
one.
> Make one state.json per collection
> ----------------------------------
>
> Key: SOLR-5473
> URL: https://issues.apache.org/jira/browse/SOLR-5473
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Noble Paul
> Assignee: Noble Paul
> Fix For: 5.0
>
> Attachments: SOLR-5473-74 .patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74.patch,
> SOLR-5473-74.patch, SOLR-5473-74.patch, SOLR-5473-74_POC.patch,
> SOLR-5473-configname-fix.patch, SOLR-5473.patch, SOLR-5473.patch,
> SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch,
> SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch,
> SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch,
> SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch,
> SOLR-5473_undo.patch, ec2-23-20-119-52_solr.log, ec2-50-16-38-73_solr.log
>
>
> As defined in the parent issue, store the states of each collection under
> /collections/collectionname/state.json node
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
