[
https://issues.apache.org/jira/browse/SOLR-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601175#comment-13601175
]
Mark Miller commented on SOLR-3755:
-----------------------------------
So to summarize - to fix this current problem, I think we want to rework the
current slice state stuff in trunk - I left open SOLR-4566 for the moment.
I think the cleanest thing for this API, and what will help keep the current
issue from reoccuring, is if we change getSlices and getSliceMap to return all
slices always.
Then we add getActiveSlices and getActiveSliceMap, and appropriate calls are
changed to that. Then there are likely to be less surprises when we try and
copy/update the clusterstate.
> shard splitting
> ---------------
>
> Key: SOLR-3755
> URL: https://issues.apache.org/jira/browse/SOLR-3755
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Yonik Seeley
> Attachments: SOLR-3755-combined.patch,
> SOLR-3755-combinedWithReplication.patch, SOLR-3755-CoreAdmin.patch,
> SOLR-3755.patch, SOLR-3755.patch, SOLR-3755.patch, SOLR-3755.patch,
> SOLR-3755-testSplitter.patch, SOLR-3755-testSplitter.patch
>
>
> We can currently easily add replicas to handle increases in query volume, but
> we should also add a way to add additional shards dynamically by splitting
> existing shards.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
