[
https://issues.apache.org/jira/browse/SOLR-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601147#comment-13601147
]
Mark Miller commented on SOLR-4566:
-----------------------------------
After chatting with Anshum in IRC, he caught me up that this stuff was newly
committed code for shard splitting. I thought it came from before that during
the clusterstate refactoring.
Which means this is not really a current bug, since nothing currently takes
advantage of slice states.
The same problems remain - getSlices should get *all* the slices. This is
critical in the clusterstate update code and just kind of what you would expect.
Another call should be added for getActiveSlices and used where appropriate.
> Fix DocCollection to return all shards not just active shards.
> --------------------------------------------------------------
>
> Key: SOLR-4566
> URL: https://issues.apache.org/jira/browse/SOLR-4566
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.3, 5.0
>
>
> I'm not sure I really like this getSlices vs getAllSclies - it's kind of easy
> to get in trouble right now I think. Some spots that we clearly want to call
> getAllSlices got left with getSlices. It's almost surprising that getSlices
> only returns active replicas - it should probably at least be called
> getSlicesWithActive or something more explicit. But for the first step, we
> should just fix the various mis calls.
> There are a couple problems around the mis calls, the most severe probably
> being that you can lose shards that are not active from the clusterstate.json
> given the right races.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]