[DOCS-11335] Document that running validation on secondary can block everything Created: 19/Feb/18 Updated: 29/Oct/23 Resolved: 06/Apr/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | 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: | 5 years, 44 weeks, 6 days ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
|
We document that the validate command takes an exclusive lock on a collection, blocking operations on that collection. We should also document that validation on a secondary can have the side effect of blocking everything on that secondary. |
| Comments |
| Comment by Githook User [ 06/Apr/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 06/Apr/18 ] |
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}Message: |