You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Alex Rodoni (JIRA)" <ji...@apache.org> on 2018/06/21 23:12:00 UTC
[jira] [Commented] (IMPALA-5763) Setting logbufsecs to 0 causes
Impala to spin on one core
[ https://issues.apache.org/jira/browse/IMPALA-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519835#comment-16519835 ]
Alex Rodoni commented on IMPALA-5763:
-------------------------------------
https://gerrit.cloudera.org/#/c/10790/
> Setting logbufsecs to 0 causes Impala to spin on one core
> ---------------------------------------------------------
>
> Key: IMPALA-5763
> URL: https://issues.apache.org/jira/browse/IMPALA-5763
> Project: IMPALA
> Issue Type: Documentation
> Components: Docs
> Affects Versions: Impala 2.9.0
> Reporter: Lars Volker
> Assignee: Alex Rodoni
> Priority: Minor
>
> Starting impalad with -logbufsecs 0 makes it spin in the thread that tries to delete old logfiles.
> [~tarmstrong], [~henryr] - Is this intended? If not, one fix would be to sleep for {{std::max(1, FLAGS_logbufsecs)}} in {{LogMaintenanceThread()}}. Another option would be to require a value >0 for logbufsecs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org