[
https://issues.apache.org/jira/browse/SOLR-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677800#comment-17677800
]
Ishan Chattopadhyaya commented on SOLR-16622:
---------------------------------------------
bq. Why was this pushed directly to the release branch with no additional
tests? Why is this ONLY pushed to branch_9_1 and not main or branch_9x first?
This is a cherry-pick of 1d7b7795cc77ad6863832e3a87d144a68490ba06 from
branch_9x (SOLR-16414) to the branch_9_1.
> 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
>
>
> 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-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
