[SERVER-31659] Investigate causal consistency violation when getting errors from config server Created: 20/Oct/17  Updated: 22/May/18  Resolved: 04/Apr/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-33954 CatalogCache refresh methods are not ... Closed
Sprint: Sharding 2018-04-09
Participants:

 Description   

Here's a breakdown of what occurred in the build failure where this appears to manifest:

1. Shard sends _configsvrCommitChunkSplit to config server.
2. Config server finish executing the command.
3. Config server steps down from primary and closes all incoming connections.
4. Shard gets back a network error and retries.
5. Shard sends the commit command and get a preCondition failure because it has already been successfully applied earlier.
6. Shard tries to inspect the state by refreshing the chunk state (by querying) but gets back the state before the commit.


Generated at Thu Feb 08 04:27:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.