[
https://issues.apache.org/jira/browse/RANGER-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18009851#comment-18009851
]
Vikas Kumar edited comment on RANGER-5266 at 7/25/25 6:34 AM:
--------------------------------------------------------------
This could be a good feature while debugging any prod issue. And this is
doable. Following could be the solution:
# First, Application needs an event that LOG level has changed
## This can be achieved in multiple way, one way is "Dynamic Configuration"
where you store such configs ( that require such dynamic loading without
restart) on Zookeeper. You update this on ZK ZNode and Application gets event
on any changes.
## Second option, Add one generic REST end point, that can be used to
dynamically update the config. Rest impl will handle second step to
update/restart .
# And based on that event , Application can update/restart the LoggerContext
after setting the new log level{{{}.{}}}
Introducing the REST endpoint seems to be an easy implementation. We may have
to update the underlying log config file as well to be in sync.
was (Author: JIRAUSER295683):
This could be a good feature while debugging any prod issue. And this is
doable. Following could be the solution:
# First, Application needs an event that LOG level has changed
## This can be achieved in multiple way, one way is "Dynamic Configuration"
where you store such configs ( that require such dynamic loading without
restart) on Zookeeper. You update this on ZK ZNode and Application gets event
on any changes.
## Second option, Add one generic REST end point, that can be used to
dynamically update the config. Rest impl will handle second step to
update/restart .
# And based on that event , Application can update/restart the LoggerContext
after setting the new log level{{{}.{}}}
Introducing the REST endpoint seems to be an easy implementation. We may have
to update the underlying log config file as well to be in sync.{{{}{}}}
{{}}
> Change log level without service restart
> ----------------------------------------
>
> Key: RANGER-5266
> URL: https://issues.apache.org/jira/browse/RANGER-5266
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
> Reporter: Fateh Singh
> Priority: Major
>
> There should be a mechanism to enable/disable DEBUG logs or other log levels
> without requiring service restart.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
