[
https://issues.apache.org/jira/browse/SOLR-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699581#comment-17699581
]
ASF subversion and git services commented on SOLR-16653:
--------------------------------------------------------
Commit 2769a77142356c4b87cc8f03decd1f3f599b6267 in solr's branch
refs/heads/branch_9x from Noble Paul
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=2769a771423 ]
SOLR-16653 : sub-shard remains inactive after split for NRT+PULL collection
(#1434)
> 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: Blocker
> Labels: pull-request-available
> Fix For: 9.2
>
> Attachments: Screenshot from 2023-02-25 06-41-17.png, Screenshot from
> 2023-02-25 06-41-25.png, Screenshot from 2023-02-25 06-43-56.png, Screenshot
> from 2023-02-27 12-17-06.png, Screenshot from 2023-02-28 12-59-01.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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
