[
https://issues.apache.org/jira/browse/SOLR-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677740#comment-17677740
]
ASF subversion and git services commented on SOLR-16622:
--------------------------------------------------------
Commit deb9e2439957dd42c349fc7fe2529d9fb63bd54d in solr's branch
refs/heads/branch_9_1 from Ishan Chattopadhyaya
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=deb9e243995 ]
SOLR-16622, SOLR-16414: simplified code / bugfix for a node restart not working
correctly
> 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
>
> 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
