[SERVER-29316] Command to verify Consistency of Indexes within a Cluster Created: 22/May/17  Updated: 22/May/17  Resolved: 22/May/17

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

Type: New Feature Priority: Major - P3
Reporter: Andrew Walsh Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-11041 Index Diagnostic Shell Helper - diag.... Open
Participants:

 Description   

Under certain circumstances, a node that is currently acting as Primary - Host A - dies suddenly during an index build process resulting in an election of a new primary - Host C. The index build then will conclude on the node that was previously primary (Host A). As Host A is not the Primary the index build isn't replicated to the other nodes and resulting inconsistent indexes between the cluster members (Host A versus B and C). Additionally, this behavior is detailed in SERVER-14746.

In these cases, it might be useful to have a command to view inconsistent indexes or indexes across the nodes in a replica set in order troubleshoot differences in behavior by running rs.checkIndexes(), for example. Such a command might also be able to be leveraged on our Cloud offerings in order to proactively identify such circumstances before an election causes a change in behavior for the customer's application.



 Comments   
Comment by Kelsey Schubert [ 22/May/17 ]

Hi andy.walsh,

Sorry, I didn't see SERVER-11041 when we discussed this earlier. I've marked it as a duplicate.

Kind regards,
Thomas

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