[
https://issues.apache.org/jira/browse/IMPALA-12073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715409#comment-17715409
]
ASF subversion and git services commented on IMPALA-12073:
----------------------------------------------------------
Commit 2750ce59d2e0d0d52f791792d5316face3bbab08 in impala's branch
refs/heads/master from ttttttz
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=2750ce59d ]
IMPALA-12073: Avoid catalogd exceptions caused by
topic_update_tbl_max_wait_time_ms being set to 1
When we set topic_update_tbl_max_wait_time_ms to 1, the topic
update thread will not work. Because this would cause the timeout
parameter to fail the validity check in the
CatalogServiceCatalog#tryLock() method. This patch avoids
this problem by allowing the timeout parameter to be 0.
Change-Id: I082c55e45e12f80738b090b8b6157a996b57002a
Reviewed-on: http://gerrit.cloudera.org:8080/19774
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Quanlong Huang <[email protected]>
> If topic_update_tbl_max_wait_time_ms is set to 1 in the catalog, the metadata
> gathering thread will not work
> ------------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-12073
> URL: https://issues.apache.org/jira/browse/IMPALA-12073
> Project: IMPALA
> Issue Type: Bug
> Reporter: Zhi Tang
> Assignee: Zhi Tang
> Priority: Major
>
> When users want the metadata gathering thread to avoid being blocked by
> table's locks as much as possible, they are likely to set
> topic_update_tbl_max_wait_time_ms to 1, which will cause the gathering thread
> to fail to work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
