-
Type:
Task
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.0.9
-
Component/s: Diagnostics, Replication
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Backport Requested:v4.0
-
Sprint:Repl 2019-04-08
Adding metrics around the size of transactions could help us determine what use cases to optimize for. Metrics for the last run transaction:
- Number of operations in the transaction
- Total size of transaction statements in oplog
- Write Concern
There will be a new serverStatus section transactions.lastCommittedTransaction:
{
|
"operationCount" : NumberLong(1),
|
"oplogOperationBytes" : NumberLong(151),
|
"writeConcern": {
|
"w" : 1,
|
"wtimeout" : 0
|
}
|
}
|
- is documented by
-
DOCS-13195 Investigate changes in SERVER-40372: Track transaction size on 4.2+
-
- Closed
-
- related to
-
SERVER-53609 lastCommittedTransaction section causes frequent schema changes that limit FTDC retention
-
- Closed
-
-
SERVER-40372 Track transaction size on 4.2+
-
- Closed
-