Skip to content

Update replica-set-elections.txt #2154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

ramsawroop420
Copy link
Contributor

added except Priority 0 members as priority 0 cannot trigger an election and the line "In the default, all members also can trigger an election" seems to suggest otherwise. Hope this is correct understanding. Do review and edit if i am right about this..

added except Priority 0 members as priority 0 cannot trigger an election and the line "In the default, all members also can trigger an election" seems to suggest otherwise. Hope this is correct understanding.  Do review and edit if i am right about this..
@kay-kim
Copy link
Contributor

kay-kim commented Feb 6, 2015

Hi -- Thank you for your pull request. I believe, however, that the current sentence is correct. By default, members have priority of 1, and as such, they can trigger an election since no member by default is priority 0. As such, will close this pull request; however, will update that section to be more clear.

Thanks again for your efforts!

Regards

@kay-kim kay-kim closed this Feb 6, 2015
@ramsawroop420
Copy link
Contributor Author

Thanks for correcting it. Can you suggest best forum where i can clarify such doubts. Being a begineer it is very important to understand the basics..

@kay-kim
Copy link
Contributor

kay-kim commented Feb 6, 2015

People tend to use stackoverflow or sometimes open a JIRA ticket if they believe there is a mistake in the docs or if the docs could be clearer or what you did (do a pull request with a suggested fix) is fine as well.

@ramsawroop420
Copy link
Contributor Author

Thank

On Friday, February 6, 2015, Kay Kim [email protected] wrote:

People tend to use stackoverflow or sometimes open a JIRA ticket if they
believe there is a mistake in the docs or if the docs could be clearer or
what you did (do a pull request with a suggested fix) is fine as well.


Reply to this email directly or view it on GitHub
#2154 (comment).

@ramsawroop420 ramsawroop420 deleted the patch-2 branch February 6, 2015 19:23
mongo-cr-bot pushed a commit that referenced this pull request Nov 17, 2022
* Add new query planner diagram

* tech review feedback

* tech review feedback 2

* final changes
mongodb-server-docs-sync-bot bot pushed a commit that referenced this pull request Jun 26, 2025
(cherry picked from commit e8046d4)

# Conflicts:
#	snooty.toml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants