[
https://issues.apache.org/jira/browse/KUDU-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bankim Bhavsar resolved KUDU-2456.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
commit f1a6335ab3a55b3838338c4591a634d761c7344f fixes the issue.
Judging by [following
email|http://mail-archives.apache.org/mod_mbox/kudu-dev/201901.mbox/%3CCAPV-%2BAw4W_AKON7RpC%3DSnEcLFTPK5Lj3t9YLgPY5bjsPnD_ojg%40mail.gmail.com%3E]
on kudu dev mailing list setting Fix Version as 1.9.0.
> TransactionTracker logs too much when there are many pending transactions
> -------------------------------------------------------------------------
>
> Key: KUDU-2456
> URL: https://issues.apache.org/jira/browse/KUDU-2456
> Project: Kudu
> Issue Type: Bug
> Components: tablet
> Affects Versions: 1.8.0
> Reporter: Adar Dembo
> Assignee: Bankim Bhavsar
> Priority: Major
> Labels: newbie
> Fix For: 1.9.0
>
> Attachments:
> 0001-KUDU-2456-Limit-number-of-pending-transactions-logge.patch
>
>
> It's possible for a tablet to have hundreds or even thousands of pending
> transactions, at which point the logging of all txns in
> TransactionTracker::WaitForAllToFinish is wasteful. Here's a snippet I saw in
> one user's cluster in the wild:
> {noformat}
> W0521 22:38:05.430140 23532 transaction_tracker.cc:227] TransactionTracker
> waiting for 1832 outstanding transactions to complete now for 6406.481s
> W0521 22:38:33.133323 23550 transaction_tracker.cc:227] TransactionTracker
> waiting for 1812 outstanding transactions to complete now for 6917.103s
> W0521 22:39:09.462368 23539 transaction_tracker.cc:227] TransactionTracker
> waiting for 1798 outstanding transactions to complete now for 6662.420s
> W0521 22:40:43.066598 23542 transaction_tracker.cc:227] TransactionTracker
> waiting for 3016 outstanding transactions to complete now for 9483.333s
> W0521 22:41:39.838529 23545 transaction_tracker.cc:227] TransactionTracker
> waiting for 3390 outstanding transactions to complete now for 9484.259s
> W0521 22:42:12.304265 23549 transaction_tracker.cc:227] TransactionTracker
> waiting for 1837 outstanding transactions to complete now for 6661.056s
> W0521 22:42:21.666013 23532 transaction_tracker.cc:227] TransactionTracker
> waiting for 1832 outstanding transactions to complete now for 6662.716s
> W0521 22:42:49.326387 23550 transaction_tracker.cc:227] TransactionTracker
> waiting for 1812 outstanding transactions to complete now for 7173.297s
> W0521 22:43:25.660738 23539 transaction_tracker.cc:227] TransactionTracker
> waiting for 1798 outstanding transactions to complete now for 6918.618s
> W0521 22:44:59.375663 23542 transaction_tracker.cc:227] TransactionTracker
> waiting for 3016 outstanding transactions to complete now for 9739.642s
> {noformat}
> Besides the spamming the log, it's not clear that these enormous lists of
> transactions are at all useful after accounting for column redaction. We
> should apply some kind of truncation here; maybe only log the first 10
> transactions or something.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
