[jira] [Assigned] (KUDU-3258) Expose some kind of transaction dashboard in ksck or the web UI
[ 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)
[jira] [Commented] (KUDU-3258) Expose some kind of transaction dashboard in ksck or the web UI
[ https://issues.apache.org/jira/browse/KUDU-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 Reviewed-by: Alexey Serbin > 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)
[jira] [Assigned] (KUDU-3269) Add UUID of the server into the metrics output
[
https://issues.apache.org/jira/browse/KUDU-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek reassigned KUDU-3269:
--
Assignee: Abhishek
> Add UUID of the server into the metrics output
> --
>
> Key: KUDU-3269
> URL: https://issues.apache.org/jira/browse/KUDU-3269
> Project: Kudu
> Issue Type: Improvement
>Reporter: Alexey Serbin
>Assignee: Abhishek
>Priority: Minor
> Labels: newbie++
>
> The server's section in the metrics output looks like the following:
> {noformat}
> {
> "type": "server",
>
> "id": "kudu.tabletserver",
>
> "attributes": {},
>
> "metrics": [ ... ]
> }
> {noformat}
> It would be great to add the UUID of the server into the output along with
> {{"type"}}, node/host name might be helpful as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (KUDU-3245) Provide Client API to set verbose logging filtered by vmodule
[
https://issues.apache.org/jira/browse/KUDU-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke reassigned KUDU-3245:
-
Assignee: Grant Henke
> Provide Client API to set verbose logging filtered by vmodule
> --
>
> Key: KUDU-3245
> URL: https://issues.apache.org/jira/browse/KUDU-3245
> Project: Kudu
> Issue Type: Improvement
> Components: client
>Reporter: Hao Hao
>Assignee: Grant Henke
>Priority: Major
>
> Similar to
> [{{client::SetVerboseLogLevel}}|https://github.com/apache/kudu/blob/master/src/kudu/client/client.h#L164]
> API, it will be nice to add another API to allow enabling verbose logging
> filtered by module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KUDU-3269) Add UUID of the server into the metrics output
[
https://issues.apache.org/jira/browse/KUDU-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-3269:
--
Labels: newbie++ (was: )
> Add UUID of the server into the metrics output
> --
>
> Key: KUDU-3269
> URL: https://issues.apache.org/jira/browse/KUDU-3269
> Project: Kudu
> Issue Type: Improvement
>Reporter: Alexey Serbin
>Priority: Minor
> Labels: newbie++
>
> The server's section in the metrics output looks like the following:
> {noformat}
> {
> "type": "server",
>
> "id": "kudu.tabletserver",
>
> "attributes": {},
>
> "metrics": [ ... ]
> }
> {noformat}
> It would be great to add the UUID of the server into the output along with
> {{"type"}}, node/host name might be helpful as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KUDU-3270) Add metrics for DNS resolution times and DNS cache-related metrics
[ https://issues.apache.org/jira/browse/KUDU-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-3270: -- Labels: roadmap-candidate (was: ) > Add metrics for DNS resolution times and DNS cache-related metrics > -- > > Key: KUDU-3270 > URL: https://issues.apache.org/jira/browse/KUDU-3270 > Project: Kudu > Issue Type: Improvement >Reporter: Alexey Serbin >Priority: Major > Labels: roadmap-candidate > > When constructing a proxy for remote peer to perform a RPC, DNS resolution is > performed. It would be great to add metrics to measure how much time the DNS > resolution takes. That information could be provided by : > * a histogram for DNS resolver times > * 'standard' cache metrics for the DNS resolver cache -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KUDU-3276) Cannot cancel transactions that have already replicated: Invalid argument: Client provided column menu_module_name STRING NULLABLE not present in tablet transaction
[ https://issues.apache.org/jira/browse/KUDU-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] matebase updated KUDU-3276: --- Fix Version/s: (was: 1.10.0) > Cannot cancel transactions that have already replicated: Invalid argument: > Client provided column menu_module_name STRING NULLABLE not present in tablet > transaction > > > Key: KUDU-3276 > URL: https://issues.apache.org/jira/browse/KUDU-3276 > Project: Kudu > Issue Type: Bug >Affects Versions: 1.10.0 >Reporter: matebase >Priority: Major > > I've seen an issue that looks as though an ADD_COLUMN is not fully applied > before performing writes. This results in a failure to bootstrap(Tablet > Server) with an error like: > T 268c5ebdc7034dffaa3a40861ce0d3ed P 004b6c262dbf49508b69c716dca5bafd S R-NP > Ts 6630181836860420096: Cannot cancel transactions that have already > replicated: Invalid argument: Client provided column menu_module_name STRING > NULLABLE not present in tablet transaction:R-NP WriteTransaction > [type=REPLICA, start_time=2021-04-19 18:02:02, state=WriteTransactionState > 0x129d4d500 [op_id=(term: 4033 index: 76346), ts=6630181836860420096, > rows=[]]] > It seems that it has been fixed in version 1.9, but this happened again when > I restarted the Tablet Server, refer to KUDU-2690 > How to manually update the field column or how to operate can solve this > problem？？ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (KUDU-3276) Cannot cancel transactions that have already replicated: Invalid argument: Client provided column menu_module_name STRING NULLABLE not present in tablet transaction
[ https://issues.apache.org/jira/browse/KUDU-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] matebase reopened KUDU-3276: > Cannot cancel transactions that have already replicated: Invalid argument: > Client provided column menu_module_name STRING NULLABLE not present in tablet > transaction > > > Key: KUDU-3276 > URL: https://issues.apache.org/jira/browse/KUDU-3276 > Project: Kudu > Issue Type: Bug >Affects Versions: 1.10.0 >Reporter: matebase >Priority: Major > Fix For: 1.10.0 > > > I've seen an issue that looks as though an ADD_COLUMN is not fully applied > before performing writes. This results in a failure to bootstrap(Tablet > Server) with an error like: > T 268c5ebdc7034dffaa3a40861ce0d3ed P 004b6c262dbf49508b69c716dca5bafd S R-NP > Ts 6630181836860420096: Cannot cancel transactions that have already > replicated: Invalid argument: Client provided column menu_module_name STRING > NULLABLE not present in tablet transaction:R-NP WriteTransaction > [type=REPLICA, start_time=2021-04-19 18:02:02, state=WriteTransactionState > 0x129d4d500 [op_id=(term: 4033 index: 76346), ts=6630181836860420096, > rows=[]]] > It seems that it has been fixed in version 1.9, but this happened again when > I restarted the Tablet Server, refer to KUDU-2690 > How to manually update the field column or how to operate can solve this > problem？？ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KUDU-3276) Cannot cancel transactions that have already replicated: Invalid argument: Client provided column menu_module_name STRING NULLABLE not present in tablet transaction
[ https://issues.apache.org/jira/browse/KUDU-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] matebase updated KUDU-3276: --- Fix Version/s: 1.10.0 Resolution: Fixed Status: Resolved (was: In Review) > Cannot cancel transactions that have already replicated: Invalid argument: > Client provided column menu_module_name STRING NULLABLE not present in tablet > transaction > > > Key: KUDU-3276 > URL: https://issues.apache.org/jira/browse/KUDU-3276 > Project: Kudu > Issue Type: Bug >Affects Versions: 1.10.0 >Reporter: matebase >Priority: Major > Fix For: 1.10.0 > > > I've seen an issue that looks as though an ADD_COLUMN is not fully applied > before performing writes. This results in a failure to bootstrap(Tablet > Server) with an error like: > T 268c5ebdc7034dffaa3a40861ce0d3ed P 004b6c262dbf49508b69c716dca5bafd S R-NP > Ts 6630181836860420096: Cannot cancel transactions that have already > replicated: Invalid argument: Client provided column menu_module_name STRING > NULLABLE not present in tablet transaction:R-NP WriteTransaction > [type=REPLICA, start_time=2021-04-19 18:02:02, state=WriteTransactionState > 0x129d4d500 [op_id=(term: 4033 index: 76346), ts=6630181836860420096, > rows=[]]] > It seems that it has been fixed in version 1.9, but this happened again when > I restarted the Tablet Server, refer to KUDU-2690 > How to manually update the field column or how to operate can solve this > problem？？ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KUDU-3276) Cannot cancel transactions that have already replicated: Invalid argument: Client provided column menu_module_name STRING NULLABLE not present in tablet transaction
[ https://issues.apache.org/jira/browse/KUDU-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] matebase updated KUDU-3276: --- Status: In Review (was: Open) > Cannot cancel transactions that have already replicated: Invalid argument: > Client provided column menu_module_name STRING NULLABLE not present in tablet > transaction > > > Key: KUDU-3276 > URL: https://issues.apache.org/jira/browse/KUDU-3276 > Project: Kudu > Issue Type: Bug >Affects Versions: 1.10.0 >Reporter: matebase >Priority: Major > > I've seen an issue that looks as though an ADD_COLUMN is not fully applied > before performing writes. This results in a failure to bootstrap(Tablet > Server) with an error like: > T 268c5ebdc7034dffaa3a40861ce0d3ed P 004b6c262dbf49508b69c716dca5bafd S R-NP > Ts 6630181836860420096: Cannot cancel transactions that have already > replicated: Invalid argument: Client provided column menu_module_name STRING > NULLABLE not present in tablet transaction:R-NP WriteTransaction > [type=REPLICA, start_time=2021-04-19 18:02:02, state=WriteTransactionState > 0x129d4d500 [op_id=(term: 4033 index: 76346), ts=6630181836860420096, > rows=[]]] > It seems that it has been fixed in version 1.9, but this happened again when > I restarted the Tablet Server, refer to KUDU-2690 > How to manually update the field column or how to operate can solve this > problem？？ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KUDU-3276) Cannot cancel transactions that have already replicated: Invalid argument: Client provided column menu_module_name STRING NULLABLE not present in tablet transaction
[ https://issues.apache.org/jira/browse/KUDU-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] matebase updated KUDU-3276: --- Description: I've seen an issue that looks as though an ADD_COLUMN is not fully applied before performing writes. This results in a failure to bootstrap(Tablet Server) with an error like: T 268c5ebdc7034dffaa3a40861ce0d3ed P 004b6c262dbf49508b69c716dca5bafd S R-NP Ts 6630181836860420096: Cannot cancel transactions that have already replicated: Invalid argument: Client provided column menu_module_name STRING NULLABLE not present in tablet transaction:R-NP WriteTransaction [type=REPLICA, start_time=2021-04-19 18:02:02, state=WriteTransactionState 0x129d4d500 [op_id=(term: 4033 index: 76346), ts=6630181836860420096, rows=[]]] It seems that it has been fixed in version 1.9, but this happened again when I restarted the Tablet Server, refer to KUDU-2690 How to manually update the field column or how to operate can solve this problem？？ was: I've seen an issue that looks as though an ADD_COLUMN is not fully applied before performing writes. This results in a failure to bootstrap(Tablet Server) with an error like: T 268c5ebdc7034dffaa3a40861ce0d3ed P 004b6c262dbf49508b69c716dca5bafd S R-NP Ts 6630181836860420096: Cannot cancel transactions that have already replicated: Invalid argument: Client provided column menu_module_name STRING NULLABLE not present in tablet transaction:R-NP WriteTransaction [type=REPLICA, start_time=2021-04-19 18:02:02, state=WriteTransactionState 0x129d4d500 [op_id=(term: 4033 index: 76346), ts=6630181836860420096, rows=[]]] How to manually update the field column or how to operate can solve this problem > Cannot cancel transactions that have already replicated: Invalid argument: > Client provided column menu_module_name STRING NULLABLE not present in tablet > transaction > > > Key: KUDU-3276 > URL: https://issues.apache.org/jira/browse/KUDU-3276 > Project: Kudu > Issue Type: Bug >Affects Versions: 1.10.0 >Reporter: matebase >Priority: Major > > I've seen an issue that looks as though an ADD_COLUMN is not fully applied > before performing writes. This results in a failure to bootstrap(Tablet > Server) with an error like: > T 268c5ebdc7034dffaa3a40861ce0d3ed P 004b6c262dbf49508b69c716dca5bafd S R-NP > Ts 6630181836860420096: Cannot cancel transactions that have already > replicated: Invalid argument: Client provided column menu_module_name STRING > NULLABLE not present in tablet transaction:R-NP WriteTransaction > [type=REPLICA, start_time=2021-04-19 18:02:02, state=WriteTransactionState > 0x129d4d500 [op_id=(term: 4033 index: 76346), ts=6630181836860420096, > rows=[]]] > It seems that it has been fixed in version 1.9, but this happened again when > I restarted the Tablet Server, refer to KUDU-2690 > How to manually update the field column or how to operate can solve this > problem？？ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KUDU-3276) Cannot cancel transactions that have already replicated: Invalid argument: Client provided column menu_module_name STRING NULLABLE not present in tablet transaction
matebase created KUDU-3276: -- Summary: Cannot cancel transactions that have already replicated: Invalid argument: Client provided column menu_module_name STRING NULLABLE not present in tablet transaction Key: KUDU-3276 URL: https://issues.apache.org/jira/browse/KUDU-3276 Project: Kudu Issue Type: Bug Affects Versions: 1.10.0 Reporter: matebase I've seen an issue that looks as though an ADD_COLUMN is not fully applied before performing writes. This results in a failure to bootstrap(Tablet Server) with an error like: T 268c5ebdc7034dffaa3a40861ce0d3ed P 004b6c262dbf49508b69c716dca5bafd S R-NP Ts 6630181836860420096: Cannot cancel transactions that have already replicated: Invalid argument: Client provided column menu_module_name STRING NULLABLE not present in tablet transaction:R-NP WriteTransaction [type=REPLICA, start_time=2021-04-19 18:02:02, state=WriteTransactionState 0x129d4d500 [op_id=(term: 4033 index: 76346), ts=6630181836860420096, rows=[]]] How to manually update the field column or how to operate can solve this problem -- This message was sent by Atlassian Jira (v8.3.4#803005)
