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 "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/08/23 21:00:00 UTC
[jira] [Resolved] (IMPALA-7433) Reduce volume of -v=1 logs on
executors
[ https://issues.apache.org/jira/browse/IMPALA-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-7433.
-----------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Reduce volume of -v=1 logs on executors
> ---------------------------------------
>
> Key: IMPALA-7433
> URL: https://issues.apache.org/jira/browse/IMPALA-7433
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 3.1.0
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Fix For: Impala 3.1.0
>
>
> We're currently logging a lot of things per query on executors that is redundant or unnecessary, e.g.:
> * ExecQueryFInstances() and StartQueryFInstances() are both logged but are redundant
> * Some random low-level details are logged, e.g. "Max row batch queue size for scan node '0' in fragment instance '940cdcd50664a51:368ab6690000001e': 180"
> I think we should cut back the logging at -v=1, which is the default log level most deployments run at:
> * Do log key finstance lifecycle events that are useful to understand what finstances are running and if/when failures occurred
> * Don't log things redundantly
> * Don't log lower-level events that occur in the normal flow of query execution (e.g. memory limits, queue lengths). These things have limited diagnostic value and should be in the profile, if anywhere
--
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