
Table 36. Default Log Levels
Component
Default Log Level
Restarting
service
required after
changing log
level?
Spark
Default log levels are controlled by
the
/opt/cray/spark/default/conf/log4j.properties
file. Default Spark settings are used when the system is
installed, but can be customized by creating a new
log4j.properties
file. A template for this can be found
in the
log4j.properties.template
file.
No
Hadoop
Default log levels are controlled by the
log4j.properties
file. Default Hadoop settings are
used when the system is installed, but can be customized
by editing the
log4j.properties
file.
Yes
Mesos
INFO
Yes
Marathon
INFO
. Log levels can be modified by editing the
log4j.properties
file.
Yes
Grafana
INFO
. Log properties can be modified by editing
the
/etc/grafana/grafana.ini
file.
Yes
Jupyter Notebook
Log levels are controlled by the
Application.log_level
configuration parameter
in
/etc/jupyterhub/jupyterhub_config.py
. It is set
to 30 by default.
Yes
Cray Graph Engine (CGE)
INFO
. The
log-reconfigure —log-level
number
command can be used to modify the log level. Use the drop
down on the CGE UI to set the log level for the specific
action being performed, i.e.
query
,
update
or
checkpoint
. Use the drop down on the Edit Server
Configuration page to set the log level. Changing the log
level in this manner persists until CGE is shut down.
No. Restarting
CGE reverts
the log level to
INFO
Flex scripts:
●
urika-yam-status
●
urika-yam-flexup
●
urika-yam-flexdown
●
urika-yam-flexdown-all
INFO
. Changing the log level for these scripts is not
supported.
NA
Spark Thrift server
INFO
.
Yes
HiverServer2
INFO
.
Yes
Tenant proxy logs
DEBUG
No
Urika-GX security manager logs
INFO
No
Troubleshooting
S3016
247