[
https://issues.apache.org/jira/browse/SOLR-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132091#comment-18132091
]
Nick Shanin commented on SOLR-6837:
-----------------------------------
>From code reading against apache/main b73f03976fa, the leader waits for
>replicas and warns about data loss
>(solr/core/src/java/org/apache/solr/cloud/ShardLeaderElectionContext.java:162,
>273). `min_rf` is now report-only
>(solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-8.adoc:329).
>Can this close as a known limit of leader-only durability?
🤖 AI-generated 🤖
> Inconsistent replicas when update is succesful against leader partitioned
> from all replicas
> -------------------------------------------------------------------------------------------
>
> Key: SOLR-6837
> URL: https://issues.apache.org/jira/browse/SOLR-6837
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.10.2
> Reporter: Shalin Shekhar Mangar
> Priority: Major
> Labels: difficulty-hard, impact-medium
>
> Refer to the following question on solr-user:
> https://www.marshut.net/kttiuz/inconsistent-doc-value-across-two-nodes-very-simple-test-what-s-the-expected-behavior.html
> {quote}
> Config
> Solr 4.7.2 / Jetty.
> SoldCloud on two nodes, and 3 ZK, all running in localhost.
> single collection: single shard with two replicas.
> Reproducing:
> start node1 9.148.58.114:8983
> start node2 9.148.58.114:8984
> Cluster state: node1 leader. node2 active.
> index value 'A' (id="change me").
> query and expect 'A' -> success
> Stop node2
> Cluster state: node1 leader. node2 gone.
> query and expect 'A' -> success
> Update document value from 'A'->'B'
> query and expect 'B' -> success
> Stop node1
> then
> Start node2.
> Cluster state: node1 gone. node2 down.
> 104510 [coreZkRegister-1-thread-1] INFO
> org.apache.solr.cloud.ShardLeaderElectionContext Waiting until we see more
> replicas up for shard shard1: total=2 found=1 timeoutin=5.27665925E14ms
> wait 3m.
> 184679 [coreZkRegister-1-thread-1] INFO
> org.apache.solr.cloud.ShardLeaderElectionContext I am the new leader:
> http://9.148.58.114:8984/solr/quick-results-collection_shard1_replica2/
> shard1
> Cluster state: node1 gone. node2 leader.
> query and expect 'A' (old value) -> success
> start node1
> Cluster state: node1 actove. node2 leader.
> Inconsistency:
> Querying node1 always returns 'B'.
> http://localhost:8983/solr/quick-results-collection_shard1_replica1/select?q=*%3A*&wt=json&indent=true
> Querying node1 always returns 'A'.
> http://localhost:8984/solr/quick-results-collection_shard1_replica2/select?q=*%3A*&wt=json&indent=true
> {quote}
> In such a case, the final steady state of the system has inconsistent
> replicas.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
