Not all master services respect 'master.service.memory.mb'
Description
In cdap-default.xml, not all of the master system services respect/use 'master.service.memory.mb' by default. For instance, stream container and log saver default to a value, regardless of what is set for 'master.service.memory.mb'.
Also, the key for log saver is inconsistent with other system containers: 'log.saver.run.memory.megs'
Release Notes
Updated more system services to respect the cdap-site parameter "master.service.memory.mb".
Additionally, deprecated "log.saver.run.memory.megs" and "log.saver.run.num.cores", in favor of "log.saver.container.memory.mb" and "log.saver.container.num.cores", respectively.
(for "Deprecated and Removed Features")
Activity
Show:
Chris GianelloniAugust 18, 2016 at 5:57 PM
The Log Saver and Explore containers are specifically set to double the normal master.service.memory.mb due to requiring more memory, they should not be changed.
In cdap-default.xml, not all of the master system services respect/use 'master.service.memory.mb' by default. For instance, stream container and log saver default to a value, regardless of what is set for 'master.service.memory.mb'.
Also, the key for log saver is inconsistent with other system containers:
'log.saver.run.memory.megs'