[DOCS-13495] [Server] Disallow 'dbHash' for nodes in RECOVERING state (SERVER-46190) Created: 05/Mar/20 Updated: 13/Nov/23 Due: 27/Mar/20 Resolved: 23/Mar/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc3, 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Andrew Feierabend (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | docs-replication | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 3 years, 48 weeks, 6 days ago | ||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||
| Description |
DescriptionDownstream Change Summary As with Description of Linked TicketIn the spirit of not allowing users to query replica set members that are not in a consistent state, we should also prohibit the use of the 'dbHash' command. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 05/Mar/20 ] |
|
Note: while this is a 4.5.1 ticket, I'm adding it to the 4.4 epic since it has a backport for 4.4. |