[
https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062112#comment-14062112
]
Noble Paul edited comment on SOLR-5473 at 7/15/14 2:27 PM:
-----------------------------------------------------------
bq. wouldn't say I am still convinced that caching till you fail is the same as
watching
You are right. caching till you fail is just an optimization in CloudSolrServer
.
According to me the client has no business to watch the state at all. The cost
of an extra request per stale state is negligible IMHO
bq.That's why I am saying that at least in the simplistic case this should be
left to configuration – watch none, all, or selected.
Yes, I'm inclined to add this (selective watch) as an option which kicks in
only if the no:of collections is greater than a certain threshold (say 10) . In
that case all Solr nodes will watch all states.
To sum it up . My preference is
# Have SolrJ do caching till it fails or till it times out (no watching
whatsoever). Please enlighten me with a case where it is risky
# SolrNodes should choose to watch all or selective based on the no:of
collections or a configurable clusterwide property
was (Author: noble.paul):
bq. wouldn't say I am still convinced that caching till you fail is the same as
watching
You are right. caching till you fail is just an optimization in CloudSolrServer
.
According to me the client has no business to watch the state at all. The cost
of an extra request per stale state is negligible IMHO
bq.That's why I am saying that at least in the simplistic case this should be
left to configuration – watch none, all, or selected.
Yes, I'm inclined to add this as an option which kicks in only if the no:of
collections is greater than a certain threshold (say 10) . In that case all
Solr nodes wil watch all states.
To sum it up . My preference is
# Have SolrJ do caching till it fails or till it times out (no watching
whatsoever). Please enlighten me with a case where it is risky
# SolrNodes should choose to watch all or selective based on the no:of
collections or a configurable clusterwide property
> Split clusterstate.json per collection and watch states selectively
> --------------------------------------------------------------------
>
> 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.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]
