[
https://issues.apache.org/jira/browse/SOLR-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653604#comment-13653604
]
Commit Tag Bot commented on SOLR-4797:
--------------------------------------
[lucene_solr_4_3 commit] shalin
http://svn.apache.org/viewvc?view=revision&revision=1480898
SOLR-4797: Shard splitting creates sub shards which have the wrong hash range
in cluster state. This happens when numShards is not a power of two and router
is compositeId
> Sub shards have wrong hash range in cluster state except when using
> PlainIdRouter
> ---------------------------------------------------------------------------------
>
> Key: SOLR-4797
> URL: https://issues.apache.org/jira/browse/SOLR-4797
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.3
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: 4.3.1
>
> Attachments: SOLR-4797.patch
>
>
> The overseer collection processor always uses PlainIdRouter to partition the
> hash range. However, some router implementations (most notably
> CompositeIdRouter) can provide a different implementation to partition hash
> ranges. So there can be a mismatch between the hash ranges which are
> persisted in clusterstate.xml for sub shards and the actual index which is
> split using the collection's configured router impl.
> This bug does not affect collections using PlainIdRouter.
> The overseer collection processor should always use the collection's
> configured router to partition ranges.
--
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]
