[ 
https://issues.apache.org/jira/browse/SOLR-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693817#comment-17693817
 ] 

ASF subversion and git services commented on SOLR-16653:
--------------------------------------------------------

Commit 5af942b6c8c2733d9418bbce7488e9fc429b5436 in solr's branch 
refs/heads/branch_9x from Noble Paul
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=5af942b6c8c ]

SOLR-16653: revert due to perf degradation (#1350)


> 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
>             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
>
>
> 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

Reply via email to