[COMPASS-1408] Can't see different indexes on primaries and secondaries Created: 22/Mar/17  Updated: 03/Oct/23  Resolved: 30/Jun/22

Status: Closed
Project: Compass
Component/s: Indexes
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Peter Schmidt Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Compass v1.8.0-beta.1 test.png    
Epic Link: COMPASS-2233

 Description   

This process allows indexes to be built on the primary and secondaries of a replica set at different times, and indeed recommends building them on secondaries first:

https://docs.mongodb.com/manual/tutorial/build-indexes-on-replica-sets/#build-indexes-on-all-secondaries

From 2017 APAC Offsite, it is anecdotally quite common to build indexes only on secondaries, e.g. for analytics workloads.

This screenshot is a test with the replica set connection in the top right Compass window, a direct connection to the primary in the bottom left window and a direct connection to the secondary in the bottom left window:

My intuition is that Compass should show some kind of merge of the two states below, e.g. perhaps a warning triangle next to the index definition to indicate which nodes have the index present.



 Comments   
Comment by Jessica Sigafoos [ 30/Jun/22 ]

Thank you for your feedback! If this issue is still relevant to you, please vote on or file a feature request at https://feedback.mongodb.com/

Comment by Sam Weaver [ 14/Jul/17 ]

This actually is an improvement that we should just do, so moving back into COMPASS queue.

Generated at Wed Feb 07 22:27:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.