[
https://issues.apache.org/jira/browse/KUDU-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wong reassigned KUDU-3258:
---------------------------------
Assignee: Andrew Wong
> 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
> Assignee: 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)
