-
Notifications
You must be signed in to change notification settings - Fork 950
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add tx queue head debug info in AnalyzeTxQueue #4026
Conversation
Signed-off-by: kostas <[email protected]>
@adiholden let's discuss here what else information we would like to print |
@@ -174,6 +178,9 @@ class EngineShard { | |||
|
|||
// the lock fingerprint with maximum contention score. | |||
uint64_t max_contention_lock; | |||
|
|||
// We can use a vector to hold debug info for all items in the txqueue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My idea here we might want to analyze the whole txqueue, so maybe it would be interesting extending DEBUG TX
to include N
transactions
{ | ||
auto value = queue->At(cur); | ||
Transaction* trx = std::get<Transaction*>(value); | ||
info.head.debug_id_info = trx->DebugId(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tx_id + name of the command + shard count. Maybe we should also include per shard data, arguments etc ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Should resolve #4020