Hi,
Using the following recommended value for app_log_dir,
"site.global.app_log_dir": "${AGENT_LOG_ROOT}/app/log",
I observed the actual log directory having deeply nested structure:
-Dhbase.log.dir=/grid/0/hdp/yarn/log/application_1403300788015_0005/container_1403300788015_0005_01_000003,/grid/1/hdp/yarn/log/application_1403300788015_0005/container_1403300788015_0005_01_000003,/grid/2/hdp/yarn/log/application_1403300788015_0005/container_1403300788015_0005_01_000003,/grid/3/hdp/yarn/log/application_1403300788015_0005/container_1403300788015_0005_01_000003,/grid/4/hdp/yarn/log/application_1403300788015_0005/container_1403300788015_0005_01_000003,/grid/5/hdp/yarn/log/application_1403300788015_0005/container_1403300788015_0005_01_000003/app/log
This was due to ApplicationConstants.Environment.LOG_DIRS containing
all possible locations for app logs.
I tried a few other options and found that the following achieves what
is desired:
"site.global.app_log_dir": "app/log",
Under
/grid/4/hdp/yarn/local/usercache/yarn/appcache/application_1403300788015_0007/container_1403300788015_0007_01_000003/app/log/,
I saw:
gc.log-201406241714
hbase-yarn-master-hor12n11.gq1.ygridcore.net.out
hbase-yarn-master-hor12n11.gq1.ygridcore.net.log SecurityAuth.audit
This is because the app log is bounded by container.
I want to get your opinion on changing recommended app_log_dir value
to reflect the above observation.
Thanks
