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

ASF subversion and git services commented on SOLR-15286:
--------------------------------------------------------

Commit 18186dcdc17cb844a87c3541e2425c7fd4fd1453 in solr's branch 
refs/heads/branch_9_0 from Anshum Gupta
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=18186dc ]

Update branch_9_0 changelog (#692)

* Cleanup CHANGES.txt on branch_9_0

* SOLR-15286: Add missing changelog entry

* Fix Changelog entries, remove some entries that no longer make sense and 
update others

* SOLR-15317: Remove change log entry from 9.0 as this was released in 8.9, 
still need to figure where to add this back

* Cleanup merge markers

> A brand new replica in the legacy setup reports healthy before replicating 
> index from its leader
> ------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-15286
>                 URL: https://issues.apache.org/jira/browse/SOLR-15286
>             Project: Solr
>          Issue Type: Bug
>          Components: replication (java)
>    Affects Versions: 8.8.1
>            Reporter: Pushkar Raste
>            Assignee: Anshum Gupta
>            Priority: Major
>             Fix For: 9.0
>
>         Attachments: SOLR-15286.patch
>
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> In the legacy mode when you add a brand new replica it immediately starts 
> reporting healthy even if it hasn't fully replicated index from its leader. 
> This issue is also exhibited when you shut down a replica and start it after 
> a lot of data is indexed on the leader.
> If the replica reports healthy LB would continue to forward incoming requests 
> to it and this would result in inconsistent data being retuned to the caller. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to