[
https://issues.apache.org/jira/browse/BIGTOP-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Leidle updated BIGTOP-1754:
-------------------------------
Description:
Right now most, if not all, Bigtop RPM packages are setup to log to
/var/log/app where app is something like hue, hadoop-yarn, or hive. Often times
systems are configured with small root partitions that can't handle this large
degree of logging. However, it is very useful to have the logs always be in
/var/log/hadoop-hdfs as this is an easy path to remember.
The proposal is that we add a global variable for defining a logging root. So
for example it could be defined as /mnt/log. If this variable is set then the
directory will be created and a symlink in var log will be created. So in the
case of hadoop-yarn:
/var/log -> /mnt/log/hadoop-yarn
would be the symlink created. All RPM specs would be updated to support this
global root logging location. For example in the hue RPM to define the log
directory variable, the definition and symlink creation would be something like
this:
LOG_DIR=$LOG_ROOT/hue
ln -sf /var/log/hue $LOG_DIR
And of course if no LOG_ROOT was defined then the log directory /var/log/hue
would be simply created as things currently work.
was:
Right now most, if not all, Bigtop RPM packages are setup to log to
/var/log/app where app is something like hue, hadoop-yarn, or hive. Often times
systems are configured with small root partitions that can't handle this large
degree of logging. However, it is very useful to have the logs always be in
/var/log/hadoop-hdfs as this is an easy path to remember.
The proposal is that we add a global variable for defining a logging root. So
for example it could be defined as /mnt/log. If this variable is set then the
directory will be created and a symlink in var log will be created. So in the
case of hadoop-yarn:
/var/log -> /mnt/log/hadoop-yarn
would be the symlink created. All RPM specs would be updated to support this
global root logging location. For example in the hue RPM to define the log
directory variable, the definition and symlink creation would be something like
this:
LOG_DIR=$LOG_ROOT/hue
ln -sf /var/log/hue ${LOG_DIR}
And of course if no LOG_ROOT was defined then the log directory /var/log/hue
would be simply created as things currently work.
> Optional global for root log directory
> --------------------------------------
>
> Key: BIGTOP-1754
> URL: https://issues.apache.org/jira/browse/BIGTOP-1754
> Project: Bigtop
> Issue Type: Improvement
> Components: debian, rpm
> Affects Versions: 0.8.0
> Reporter: Rob Leidle
> Priority: Minor
> Fix For: backlog
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Right now most, if not all, Bigtop RPM packages are setup to log to
> /var/log/app where app is something like hue, hadoop-yarn, or hive. Often
> times systems are configured with small root partitions that can't handle
> this large degree of logging. However, it is very useful to have the logs
> always be in /var/log/hadoop-hdfs as this is an easy path to remember.
> The proposal is that we add a global variable for defining a logging root. So
> for example it could be defined as /mnt/log. If this variable is set then the
> directory will be created and a symlink in var log will be created. So in the
> case of hadoop-yarn:
> /var/log -> /mnt/log/hadoop-yarn
> would be the symlink created. All RPM specs would be updated to support this
> global root logging location. For example in the hue RPM to define the log
> directory variable, the definition and symlink creation would be something
> like this:
> LOG_DIR=$LOG_ROOT/hue
> ln -sf /var/log/hue $LOG_DIR
> And of course if no LOG_ROOT was defined then the log directory /var/log/hue
> would be simply created as things currently work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
