[SERVER-7846] Have Nodes report if they can be used as a seed Created: 04/Dec/12  Updated: 08/Mar/13  Resolved: 15/Dec/12

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

Type: New Feature Priority: Minor - P4
Reporter: David Hows Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:

 Description   

Currently there are a few edge cases where a node is not PRIMARY or SECONDARY but does contain a valid data for being used as a seed node.

In order to validate this trustworthiness we currently only trust PRIMARY or SECONDARY nodes is can we have another mechanism which will allow us to confirm the data from a different node is trustworthy.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 15/Dec/12 ]

There isn't a "is seed" concept.
If they have a config, ismaster will return other nodes.
Otherwise it'll just have nothing, so its obvious.

Comment by Scott Hernandez (Inactive) [ 04/Dec/12 ]

What us the use-case for this. When is a node able to be a seed when you don't want it to be?

If the node isn't secondary/primary then what state was it in?

Is this just for client replica set membership discovery? Or is this related to replication and nodes?

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