[
https://issues.apache.org/jira/browse/KUDU-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325306#comment-17325306
]
ASF subversion and git services commented on KUDU-3258:
-------------------------------------------------------
Commit bdb6d0643ec7b68f11cefc038dc256824ce96f5e in kudu's branch
refs/heads/master from Andrew Wong
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=bdb6d06 ]
[ksck] KUDU-3258: allow ksck and rebalancer to work on txn status table
This patch adds the transaction system table to the ksck output in its
own section for system tables. Here's a sample snippet of an output that
has the system table:
Summary by system table
Name | RF | Status | Total Tablets |
Healthy | Recovering | Under-replicated | Unavailable
-------------------------------+----+------------------+---------------+---------+------------+------------------+-------------
kudu_system.kudu_transactions | 3 | UNDER_REPLICATED | 1 | 0
| 0 | 1 | 0
Summary by table
Name | RF | Status |
Total Tablets | Healthy | Recovering | Under-replicated | Unavailable
-------------------------------------------------------+----+-------------+---------------+---------+------------+------------------+-------------
default.loadgen_auto_05cf5be513ea4a84a052e8044f641c1a | 1 | UNAVAILABLE | 8
| 6 | 0 | 0 | 2
default.loadgen_auto_0c7ea48d5f6948408694b176f70e69ec | 1 | UNAVAILABLE | 8
| 5 | 0 | 0 | 3
default.loadgen_auto_241be343981c46d081ab2b3d2e3b6e6a | 1 | UNAVAILABLE | 8
| 5 | 0 | 0 | 3
default.loadgen_auto_385476d5d3b6493f8cbf659c8a4cf7cc | 1 | UNAVAILABLE | 8
| 6 | 0 | 0 | 2
default.loadgen_auto_430e280e8aa7450591da67ae15ff0f37 | 1 | UNAVAILABLE | 8
| 6 | 0 | 0 | 2
The section can be included/excluded via the --sections flag of ksck.
Since ksck and the rebalancer use the same cluster-examining code, this
patch also updates the rebalancer cluster_status class to account for
system tables -- the tool would have crashed upon trying to find the
replication factor of the system table otherwise.
Change-Id: I8162f6eb046d98791c6bdeb5c15a0af72487300d
Reviewed-on: http://gerrit.cloudera.org:8080/17315
Tested-by: Andrew Wong <aw...@cloudera.com>
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
> Expose some kind of transaction dashboard in ksck or the web UI
> ---------------------------------------------------------------
>
> Key: KUDU-3258
> URL: https://issues.apache.org/jira/browse/KUDU-3258
> Project: Kudu
> Issue Type: Improvement
> Components: ops-tooling, transactions
> Reporter: Andrew Wong
> Priority: Major
>
> It would be useful to expose the locations and tablet IDs of the
> TxnStatusManager replicas, and even show the health of them from unified
> front, whether that's the web UI, ksck, or both. Some useful things to know
> about:
> - The tablet ID, range, and location of each TxnStatusManager partition
> - The highest transaction ID per TxnStatusManager partition
> - In-flight (not COMMITTED or ABORTED) transactions and their current state,
> though would also be nice to filter specific states
> - Commit timestamp (and other relevant timestamps, if available, reported
> with physical and logical portions)
> - We could also consider storing the transaction creation time in the same
> way that we have a "time created" for tables in the masters
> After some discussion with Alexey, we think it'd be more useful to focus on:
> * having a separate section in ksck to display the health of the transaction
> status table
> * having a separate tool to focus on displaying the business logic of the
> TxnStatusManager partitions (not the web UI, for now)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
