[SERVER-21707] slowms should include time spent waiting for writeConcern fulfillment Created: 01/Dec/15 Updated: 01/Dec/15 Resolved: 01/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
mongoD slowms logging includes time spent waiting for writeConcern fulfillment. It does not currently split out the time spent executing the write locally vs. time spent waiting for replication when w >= 2. We should provide the write concern wait time separately to allow for easier diagnosis when slow. The following is an example of an insert that spent 1000ms waiting for write concern acknowledgement (before timing out).
|
| Comments |
| Comment by Scott Hernandez (Inactive) [ 01/Dec/15 ] |
|
dup of |