[jira] [Assigned] (KUDU-2730) ReadMaxCpuIndex doesn't include possible hotplugged CPUs

[ https://issues.apache.org/jira/browse/KUDU-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong reassigned KUDU-2730: --- Assignee: (was: Tim Armstrong) > ReadMaxCpuIndex doesn't include possible hotplugged CPUs

[jira] [Commented] (KUDU-2718) master_failover-itest when HMS is enabled is flaky

[ https://issues.apache.org/jira/browse/KUDU-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810218#comment-16810218 ] Hao Hao commented on KUDU-2718: --- DropTable in HMS is a synchronous call, so I think it shoul

[jira] [Updated] (KUDU-2763) Confusing "log matching property violated" message on new tablets

[ https://issues.apache.org/jira/browse/KUDU-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated KUDU-2763: -- Labels: newbie (was: ) > Confusing "log matching property violated" message on new tablets > --

[jira] [Created] (KUDU-2763) Confusing "log matching property violated" message on new tablets

Todd Lipcon created KUDU-2763: - Summary: Confusing "log matching property violated" message on new tablets Key: KUDU-2763 URL: https://issues.apache.org/jira/browse/KUDU-2763 Project: Kudu Issue

[jira] [Commented] (KUDU-2760) kudu-tool-test.TestCopyTable is flaky

[ https://issues.apache.org/jira/browse/KUDU-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809687#comment-16809687 ] Yingchun Lai commented on KUDU-2760: This PR fix it https://gerrit.cloudera.org/#/c/12

[jira] [Assigned] (KUDU-2760) kudu-tool-test.TestCopyTable is flaky

[ https://issues.apache.org/jira/browse/KUDU-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yingchun Lai reassigned KUDU-2760: -- Assignee: Yingchun Lai > kudu-tool-test.TestCopyTable is flaky > --