[SERVER-6587] Allow replica set secondaries to be used in non-default ways, with work loads like analytics Created: 25/Jul/12  Updated: 10/Aug/13  Resolved: 10/Aug/13

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Replication
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: siddharth.singh@10gen.com Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-3664 Allow different indexes on replica se... Backlog
Participants:

 Description   

Right now, for a replica secondary to work in a non-default way (eg. creating specific indexes directly on a analytics replica node and not on the entire replica set)
requires restarting replica set members without --replSet, performing the desired operation and then putting it back as a replica set member. This is kind of cumbersome with lots of caveats. Would be nice to support this feature to work in such scenarios.



 Comments   
Comment by Scott Hernandez (Inactive) [ 25/Jul/12 ]

This should probably require the node to priority 0.

It might be good to put these into some kind of maintenance mode (or alternate use mode) where write restrictions are lifted and whereit tracks if any writes are done so these nodes are marked as dirty and they can't be accidentally reconfigured back into non-priority 0 nodes, and become primary.

Generated at Thu Feb 08 03:12:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.