[SERVER-15406] Report write concern progress in currentOp Created: 25/Sep/14 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Admin, Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Description |
|
We only report that an op is "waiting for write concern" but not its progress. We should update the message as we wait to provide progress on steps completed and pending. Example op wait for w:2 on a 1 node repica set:
Currently we set the status here:
|
| Comments |
| Comment by Scott Hernandez (Inactive) [ 08/Mar/16 ] | ||||||
|
I was thinking local, but we can fill that out as needed and with what info we have. The idea is that we can account for all write concern options, including replication – see even if "w" is not specified we can still see things waiting for local resources (the message kinda covers this now I think). | ||||||
| Comment by Eric Milkie [ 08/Mar/16 ] | ||||||
|
That's a good start, although I'm not sure what "journal" means. Local, or across the cluster? | ||||||
| Comment by Scott Hernandez (Inactive) [ 08/Mar/16 ] | ||||||
|
I'm open to any form of progress, but was thinking of something like this:
| ||||||
| Comment by Eric Milkie [ 08/Mar/16 ] | ||||||
|
What kind of progress can we report; would you put the actual write concern being waited for, or the number of nodes remaining that haven't responded yet, or some other thing? |