[
https://issues.apache.org/jira/browse/SOLR-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690885#comment-17690885
]
Ishan Chattopadhyaya commented on SOLR-16653:
---------------------------------------------
[~noble.paul], [~hiteshkhamesra], we should always use JIRA number in the
commit messages, so that they are easy to cross-reference.
> Shard split doesn't work when shard has NRT and pull replica and prs is
> enable on collection
> --------------------------------------------------------------------------------------------
>
> Key: SOLR-16653
> URL: https://issues.apache.org/jira/browse/SOLR-16653
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 9.1.1
> Reporter: Hitesh Khamesra
> Assignee: Noble Paul
> Priority: Major
> Labels: pull-request-available
>
> To reproduce shard shard split scenario
> # create a collection with PRS enable
> # create shard with NRT and pull replica
> # execute a shard split cmd
> # result: subshard will not become active
>
> Problem: We observed that prs state of replica is updated by data node. But
> overseer node doesn't listen/read that updated prs state of replica. because
> of that subshard remains inactive after shard split.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
