[SERVER-46727] Shutdown the secondary node from the replica set that is behind XX seconds Created: 09/Mar/20 Updated: 22/Apr/20 Resolved: 22/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Vinicius Grippa | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
MongoDB 4.2 introduced the FlowControl feature. However, it might be interesting to have something that makes this node hidden or take it out of the cluster when it starts falling behind the primary and/or other secondary nodes after a certain number of seconds. There are the majority/local and other types of read concern, but this won't help.
For example: If I have 3 nodes and one is starting to fall behind (due to a backup for example), I want my mongoS redirecting the reads for the other nodes. Setting it to hidden permanent is not an option because I lose hardware resources for it most of the time (because the node will be available only for backup).
|
| Comments |
| Comment by Eric Sedor [ 22/Apr/20 ] |
|
Thanks vgrippa@gmail.com! |
| Comment by Vinicius Grippa [ 21/Apr/20 ] |
|
Hi Eric,
Sorry for the delay. I believe that maxStalenessSeconds will fit for this case. Thanks for your help. We can close the case.
|
| Comment by Eric Sedor [ 21/Apr/20 ] |
|
Hi vgrippa@gmail.com, can you let us know if maxStalenessSeconds helps or not? |
| Comment by Eric Sedor [ 10/Mar/20 ] |
|
Read Preference maxStalenessSeconds should help with this. Can you take a look and let us know if it's what you are looking for? Sincerely, |