[SERVER-51321] [polish] include information about client that created tenant migration donor in currOp Created: 02/Oct/20 Updated: 06/Dec/22 Resolved: 08/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jason Zhang | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | pm-1791_non-cloud-blocking, pm-1791_polish | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
This is the currentOp output for a tenant migration donor: The donorStartMigration command creates a POS instance that runs in the background in a thread pool. Would it be useful to include information about the client of the donorStartMigration command? A proposed output:
|
| Comments |
| Comment by Esha Maharishi (Inactive) [ 02/Oct/20 ] |
|
bruce.lucas, the currentOp output for TransactionCoordinators includes the client metadata for the last Client that updated the TransactionCoordinator. We were wondering if this has been useful, or if you think it would be useful for TenantMigrationDonors? |