[
https://issues.apache.org/jira/browse/HIVE-16285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939263#comment-15939263
]
Prasanth Jayachandran commented on HIVE-16285:
----------------------------------------------
Removed all the statics that holds log level enable states. This used to be a
problem with old log4j 1.x. With log4j2 calls to Log.isInfoEnabled() (also
other levels) are very cheap (very few nano seconds -
https://logging.apache.org/log4j/log4j-2.2/performance.html). Also branch
predictors should do a good job with such conditions in inner loops.
> Servlet for dynamically configuring log levels
> ----------------------------------------------
>
> Key: HIVE-16285
> URL: https://issues.apache.org/jira/browse/HIVE-16285
> Project: Hive
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 2.2.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Attachments: HIVE-16285.1.patch
>
>
> Many long running services like HS2, LLAP etc. will benefit from having an
> endpoint to dynamically change log levels for various loggers. This will help
> greatly with debuggability without requiring a restart of the service.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
