Hello Will Berkeley, Mike Percy, I'd like you to do a code review. Please visit
http://gerrit.cloudera.org:8080/11765 to review the following change. Change subject: transaction_tracker: add more information to the out-of-memory message ...................................................................... transaction_tracker: add more information to the out-of-memory message A Slack user reported seeing an error like this: transaction_tracker.cc:119] Transaction failed, tablet \ 00000000000000000000000000000000 transaction memory consumption (0) has \ exceeded its limit (67108864) or the limit of an ancestral tracker This doesn't make sense; how could the limit be exceeded if the consumption is 0? As far as I can tell, it can only happen if the failed transaction had a colossal footprint of its own. This patch changes the generated error to include the footprint of the transaction itself. Change-Id: Ic4017c1aecec29cd4b4b04c15efa4bf38c925cb9 --- M src/kudu/tablet/transactions/transaction_tracker.cc 1 file changed, 4 insertions(+), 3 deletions(-) git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/65/11765/1 -- To view, visit http://gerrit.cloudera.org:8080/11765 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: newchange Gerrit-Change-Id: Ic4017c1aecec29cd4b4b04c15efa4bf38c925cb9 Gerrit-Change-Number: 11765 Gerrit-PatchSet: 1 Gerrit-Owner: Adar Dembo <a...@cloudera.com> Gerrit-Reviewer: Mike Percy <mpe...@apache.org> Gerrit-Reviewer: Will Berkeley <wdberke...@gmail.com>