[
https://issues.apache.org/jira/browse/SOLR-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677786#comment-17677786
]
Michael Gibney commented on SOLR-16622:
---------------------------------------
Thanks for catching this and backporting. I will prepare RC2 for 9.1.1 shortly.
{quote}Turns out there was a commit (SOLR-16414) that escaped all testing{quote}
To probe this a little bit: there were multiple commits on SOLR-16414; I'm
curious whether you have any insight into what the specific cause of the issue
may have been? Looking at the diff for the change that ended up fixing this
issue, I wonder if possibly [wrapping
exceptions|https://github.com/apache/solr/commit/deb9e243995#diff-5b63503605ede4384429e74d1fa0c410adc5da8f3246e8c36e49feff2f3ea692L2969-L2971]
may have messed with exception handling/retries?
> 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
