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

Posted to issues@solr.apache.org by "Ishan Chattopadhyaya (Jira)" <ji...@apache.org> on 2023/01/17 15:21:00 UTC

[jira] [Updated] (SOLR-16622) Replicas don't come up active after node restart

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

Ishan Chattopadhyaya updated SOLR-16622:
----------------------------------------
    Attachment: Screenshot from 2023-01-17 15-03-05.png

> Replicas don't come up active after node restart
> ------------------------------------------------
>
>                 Key: SOLR-16622
>                 URL: https://issues.apache.org/jira/browse/SOLR-16622
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Ishan Chattopadhyaya
>            Priority: Major
>             Fix For: 9.1.1
>
>         Attachments: Screenshot from 2023-01-17 15-03-05.png
>
>
> While benchmarking for performance, we saw a sharp change in the graphs:
> https://issues.apache.org/jira/browse/SOLR-16525?focusedCommentId=17676725&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17676725
> Turns out there was a commit (SOLR-16414) that escaped all testing and caused a regression where restarted nodes didn't have the replicas coming up as active.
> This affects 9.1 release, so opening a new JIRA issue to track it.



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