[ 
https://issues.apache.org/jira/browse/SOLR-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677806#comment-17677806
 ] 

Ishan Chattopadhyaya commented on SOLR-16622:
---------------------------------------------

bq. I'm curious whether you have any insight into what the specific cause of 
the issue may have been?

I can only attest to the effect of what I saw, haven't yet dug into what the 
problem actually was. The commit 
https://gitbox.apache.org/repos/asf?p=solr.git;h=97e5483cb6b (SOLR-16414) 
caused Solr nodes to come up in stress tests, but querying them was not 
possible because two of the three replicas (shard2 and shard3) were in down 
state. Also, additionally, there was PRS like structure to a non-PRS 
collection.  !Screenshot from 2023-01-17 15-03-05.png! 

Since from the graphs we knew the problem was corrected by itself at a later 
point, all I had to do was to find the commit that fixed it (by looking at the 
graph). This was the first commit that fixed it: 
https://gitbox.apache.org/repos/asf?p=solr.git;h=1d7b7795cc7, so backported it. 
I manually tested that the state.json structure was proper as well.

> 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-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to