You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "Noble Paul (Jira)" <ji...@apache.org> on 2022/10/17 05:58:00 UTC

[jira] [Resolved] (SOLR-16447) PRS entry should not be updated by overseer

     [ https://issues.apache.org/jira/browse/SOLR-16447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Noble Paul resolved SOLR-16447.
-------------------------------
    Resolution: Implemented

this is already fixed asa part of SOLR-16440

> PRS entry should not be updated by overseer
> -------------------------------------------
>
>                 Key: SOLR-16447
>                 URL: https://issues.apache.org/jira/browse/SOLR-16447
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: Hitesh Khamesra
>            Assignee: Noble Paul
>            Priority: Blocker
>             Fix For: 9.1
>
>
> ReplicaMutator updates the prs entry, which happens through overseer node. But there are race condition, when replicas direct updates the prs state at the same time, which can lead to dirty prs state. Ideally prs state should be updated by datanode(or replica) only



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org