You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2018/02/16 14:11:00 UTC
[jira] [Updated] (KUDU-1912) Tablet startup fails on transaction
memory consumption
[ https://issues.apache.org/jira/browse/KUDU-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KUDU-1912:
------------------------------
Target Version/s: (was: 1.5.0)
> Tablet startup fails on transaction memory consumption
> ------------------------------------------------------
>
> Key: KUDU-1912
> URL: https://issues.apache.org/jira/browse/KUDU-1912
> Project: Kudu
> Issue Type: Bug
> Components: tablet
> Affects Versions: 1.2.0
> Reporter: Jean-Daniel Cryans
> Priority: Major
>
> As reported by a user on Slack:
> {code}
> W0307 20:03:46.820791 25594 transaction_tracker.cc:108] Transaction failed, tablet 7bb5e24d7521458d91ad06736a9f7685 transaction memory consumption (66447925) has exceeded its limit (67108864) or the limit of an ancestral tracker
> E0307 20:03:46.820821 25594 ts_tablet_manager.cc:776] T 7bb5e24d7521458d91ad06736a9f7685 P d4a26cb0d6994266a68dc76d983e454a: Tablet failed to start: Service unavailable: Transaction failed, tablet 7bb5e24d7521458d91ad06736a9f7685 transaction memory consumption (66447925) has exceeded its limit (67108864) or the limit of an ancestral tracker
> {code}
> Then since it's a failed state, the replica doesn't get kicked out of the configuration and so the tablet stays under-replicated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)