[jira] [Updated] (RANGER-4124) Value of -Dlogback.configurationFile in ranger-tagsync-services.sh is not configurable

["Madhan Neethiraj (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RANGER-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Madhan Neethiraj updated RANGER-4124:
-------------------------------------
    Fix Version/s: 2.4.1

> Value of -Dlogback.configurationFile in ranger-tagsync-services.sh  is not configurable
> ---------------------------------------------------------------------------------------
>
>                 Key: RANGER-4124
>                 URL: https://issues.apache.org/jira/browse/RANGER-4124
>             Project: Ranger
>          Issue Type: Improvement
>          Components: tagsync
>            Reporter: Lei Yao
>            Assignee: Lei Yao
>            Priority: Minor
>             Fix For: 3.0.0, 2.4.1
>
>         Attachments: 0001-RANGER-4124-Value-of-Dlogback.configurationFile-in-r.patch
>
>
> In file ranger-tagsync-services.sh，we can find -Dlogback.configurationFile not configurable
> {code:java}
> nohup java -Dproc_rangertagsync ${JAVA_OPTS} -Dlogdir="${RANGER_TAGSYNC_LOG_DIR}" -Dlogback.configurationFile=file:/etc/ranger/tagsync/conf/logback.xml -cp "${cp}" org.apache.ranger.tagsync.process.TagSynchronizer  > ${RANGER_TAGSYNC_LOG_DIR}/tagsync.out 2>&1 &
> {code}
> Like  usersync， suggest add variable TAGSYNC_CONF_DIR  and set  -Dlogback.configurationFile=file:${TAGSYNC_CONF_DIR}/logback.xml
> After applying this patch, we can support customization setting for logback.xml location in cluster management tools like Ambari.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)