[
https://issues.apache.org/jira/browse/SOLR-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069846#comment-15069846
]
Christine Poerschke commented on SOLR-5209:
-------------------------------------------
[[email protected]] - if you have no objections then I will re-assign this
ticket to myself with a view towards committing it in the first half of January
or so, to trunk (and not branch_5x) in good time for the 6.0.0 release
hopefully, after reviews of course.
Everyone - the latest {{SOLR-5209.patch}} attachment contains the (small)
change itself, a new {{OverseerTest.testRemovalOfLastReplica()}} test plus
adjustments to existing tests. Reviews, comments, suggestions etc. welcome.
Thank you.
> last replica removal cascades to remove shard from clusterstate
> ---------------------------------------------------------------
>
> Key: SOLR-5209
> URL: https://issues.apache.org/jira/browse/SOLR-5209
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.4
> Reporter: Christine Poerschke
> Assignee: Mark Miller
> Priority: Blocker
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-5209.patch, SOLR-5209.patch
>
>
> The problem we saw was that unloading of an only replica of a shard deleted
> that shard's info from the clusterstate. Once it was gone then there was no
> easy way to re-create the shard (other than dropping and re-creating the
> whole collection's state).
> This seems like a bug?
> Overseer.java around line 600 has a comment and commented out code:
> // TODO TODO TODO!!! if there are no replicas left for the slice, and the
> slice has no hash range, remove it
> // if (newReplicas.size() == 0 && slice.getRange() == null) {
> // if there are no replicas left for the slice remove it
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
