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 "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/22 17:35:01 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=16775423#comment-16775423 ]
ASF subversion and git services commented on IMPALA-5763:
---------------------------------------------------------
Commit f3761d449b5e0e4247a71334b43ae7d7fc3d4f7b in impala's branch refs/heads/2.x from Alex Rodoni
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=f3761d4 ]
IMPALA-5763: [DOCS] Warn against setting --logbufsecs to 0
Change-Id: I45d14e2ba601574cf76a4b739617b097f3e551aa
Reviewed-on: http://gerrit.cloudera.org:8080/10790
Reviewed-by: Tim Armstrong <ta...@cloudera.com>
Reviewed-by: Lars Volker <lv...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> 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
> Fix For: Impala 2.13.0, Impala 3.1.0
>
>
> 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