[
https://issues.apache.org/jira/browse/IMPALA-9787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17119144#comment-17119144
]
ASF subversion and git services commented on IMPALA-9787:
---------------------------------------------------------
Commit a1485177d45df304ba16f158a871287c1415da91 in impala's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=a148517 ]
IMPALA-9787: fix spinning thread with memory-based table invalidation
Testing:
Before this fix, CPU usage for catalogd in my local env with
-invalidate_tables_on_memory_pressure was 100%.
After this fix, CPU usage for the catalogd was low.
Change-Id: I47d0cfc40ed7247e96322f9533fa594a03d7a8a3
Reviewed-on: http://gerrit.cloudera.org:8080/15994
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Catalog spins on one core when memory-based invalidation is enabled
> -------------------------------------------------------------------
>
> Key: IMPALA-9787
> URL: https://issues.apache.org/jira/browse/IMPALA-9787
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 3.0, Impala 3.1.0, Impala 3.2.0, Impala 3.3.0,
> Impala 3.4.0
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Critical
>
> When I start up a catalogd with -invalidate_tables_on_memory_pressure=true
> but -invalidate_tables_timeout_s not set, one thread just spins and eats up a
> full core.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
