[SERVER-82595] Consider adding ordered vs. unordered info and any other interesting info for bulkWrite to serverStatus Created: 30/Oct/23 Updated: 22/Jan/24 |
|
| Status: | Investigating |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaitlin Mahar | Assignee: | Alan Zheng |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pmr | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
It might be useful to add information to serverStatus on how many bulkWrites are done with ordered=true vs ordered=false. We've thought a lot about the "many write errors" edge case for bulkWrite throughout this project and in the future it could be helpful from a product perspective to know how commonly used unordered bulkWrite is. If we did that, we might want to file a ticket about adding a similar stat for insert/update/delete. We could also consider other things like "how many bulkWrites target multiple namespaces" or "how many bulkWrites mix op types". We can also always add more things later, but we should consider now if there is any info we definitely want right off the bat. |
| Comments |
| Comment by Sean Zimmerman [ 18/Jan/24 ] |
|
Removing this from PM-1452 since it is only a nice to have and shouldn't block project completion and reassignment of engineers. We can either do this eventually ourselves or make this ticket more generic to include metrics for insert/update/delete as well and send it to query |