[
https://issues.apache.org/jira/browse/SOLR-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132108#comment-18132108
]
Nick Shanin commented on SOLR-9369:
-----------------------------------
>From code reading against apache/main b73f03976fa, the `commitTimeMSec`
>equality check compares a value copied with the leader's segments file, not
>two clocks
>(solr/core/src/java/org/apache/solr/handler/IndexFetcher.java:611-617). A
>candidate is to replace the TODO with that reason and leave the behaviour as
>is. Is that still an open concern?
🤖 AI-generated 🤖
> SolrCloud should not compare commitTimeMSec to see if replicas are in sync
> --------------------------------------------------------------------------
>
> Key: SOLR-9369
> URL: https://issues.apache.org/jira/browse/SOLR-9369
> Project: Solr
> Issue Type: Bug
> Reporter: Varun Thacker
> Priority: Major
>
> Today the replication code we compare if two replicas are in sync by checking
> the commit timestamp ( "commitTimeMSec" )
> This made sense for master slave but I don't think is useful for SolrCloud
> since different replicas will commit at different times. We should not check
> for this in SolrCloud mode.
> Ramkumar noted this on SOLR-7859 as well.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
