[DOCS-13157] Investigate changes in SERVER-30357: Allow users to run the validate cmd with {background:true} Created: 21/Oct/19 Updated: 13/Nov/23 Resolved: 05/Feb/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, 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: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||
| Days since reply: | 3 years, 33 weeks, 1 day ago | ||||||||||||||||||||||||||||||||||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||||||||||||||||||||||||||||||||||
| Description |
DescriptionDownstream Change Summary The validate cmd can now run {background:true}. The default for the background parameter is false. {background:true} and {full:true} are incompatible: only one or the other may be true in a single cmd. Background validation can run concurrently with CRUD and DDL operations. It periodically yields locks to allow CRUD and DDL ops to run concurrently, and will return an error if the collection or an index is dropped that it is validating. Background validation only runs on checkpoint'ed data, which is only supported by the 'wiredTiger' storage engine, and so background validation is only supported on the 'wiredTiger' storage engine. If a collection has not yet been checkpoint'ed, then the validate cmd benignly returns ok:1 with valid:true and only a warning in the 'warning' field. If an index is too newly created to have been checkpoint'ed, then validate w/ background:true will ignore it (won't run validation on it). If an index has been checkpoint'ed, but dropped and the drop hasn't yet been checkpoint'ed, then that index will be ignored as well: no point validating a dropped index. Description of Linked TicketInstead of the existing code
in validate.cpp, we will parse the user cmd request's "background" field and initialize it with that value. If unspecified, "background" defaults to false. Additionally, return an error if {full:true} is specified along with {background:true}. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 23/Jun/20 ] |
|
Author: {'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: Revert " This reverts commit 931f303d1ccc9fec16dfb466d1c76133242a257c. |
| Comment by Githook User [ 05/Feb/20 ] |
|
Author: {'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}Message: |
| Comment by Kay Kim (Inactive) [ 30/Jan/20 ] |
|
Will do. I'll do the background validation docs in 2 parts. Part 1: to lay the groundwork, with regards to the validate() parameters, etc. - |
| Comment by Dianna Hohensee (Inactive) [ 21/Oct/19 ] |
|
Let me know if you need more information about checkpoints. I think checkpoints will have to be explained to a certain degree for the user to understand what background validation is running against. |