Clarify the need to specify priority: 0 for hidden secondaries #1516
+2
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I found the previous wording suggestive that priority: 0 would be implied if not specified when hidden: true. I prefer this wording, as I feel it makes clearer the need for priority: 0 to be explicitly specified (even though it's not much of a change).
|
merged. thank you! |
mongo-cr-bot
pushed a commit
that referenced
this pull request
Jul 27, 2022
* DOCSP-13706 adding delay clarification * DOCSP-13706 adding -that- for consistency * DOCSP-13706 adding ttl deletion clarification * DOCSP-13706 adding -start- for context * DOCSP-13706 updating tense for context * DOCSP-13706 tech review comment implemented
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 26, 2025
* (DOCSP-32503) Resolving naming conflict. * (DOCSP-32503) Adding back yaml files for option generation. * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * Empty commit to test build. * (DOCSP-32503) * (DOCSP-32503) * Empty commit for build testing. * Empty commit for build testing. * (DOCSP-32503) * (DOCSP-32503) Ensure all affinity settings are explicitly included. If they are not, they will not be parsed properly and references via the setting directive will fail. * (DOCSP-32503) Tech review. * (DOCSP-32503) Copy review, part 1 * (DOCSP-32503) Copy review, part 2 * (DOCSP-32503) Copy review. * (DOCSP-32503) Copy review, Part 4
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 26, 2025
* (DOCSP-32503) Resolving naming conflict. * (DOCSP-32503) Adding back yaml files for option generation. * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * (DOCSP-32503) * Empty commit to test build. * (DOCSP-32503) * (DOCSP-32503) * Empty commit for build testing. * Empty commit for build testing. * (DOCSP-32503) * (DOCSP-32503) Ensure all affinity settings are explicitly included. If they are not, they will not be parsed properly and references via the setting directive will fail. * (DOCSP-32503) Tech review. * (DOCSP-32503) Copy review, part 1 * (DOCSP-32503) Copy review, part 2 * (DOCSP-32503) Copy review. * (DOCSP-32503) Copy review, Part 4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found the previous wording suggestive that priority: 0 would be implied if not specified when hidden: true. I prefer this wording, as I feel it makes clearer the need for priority: 0 to be explicitly specified (even though it's not much of a change).