warden.conf configuration file is associated with standard services provided by MapR. Warden supports service monitoring for these additional services:
- hbase thrift server (Supported with
- hbase rest gateway (Supported with
- hive metastore
- spark master
Each of these supported services requires a configuration file,
warden.<servicename>.conf, which is included with the package for that service. When you install one of these service packages, its corresponding configuration file is stored in
/opt/mapr/conf/conf.d. The configuration files and their packages are shown below:
|Service Name||Configuration File||Comments|
|gateway||warden.gateway.conf||Installed with the |
|drill||warden.drill-bits.conf||Installed with the |
|hue||Installed with the |
|httpfs||Installed with the |
|hbase thrift server||Installed with the |
|hbase rest gateway||Installed with the |
|historyserver||Installed with the |
|hive metastore||Installed with the |
|hiveserver2||Installed with the |
|nodemanager||Installed with the |
|oozie||Installed with the |
|resourcemanager||Installed with the |
|spark master||Installed with the |
The following properties can be in a
|services||Service name and number of nodes this service should run on, along with service dependencies. Format is |
|service.displayname||Service display name to appear in UI|
|service.command.type||Indicates whether the script runs in background (and exits) or inline (script does not exit). Type is |
|service.command.monitor||Monitors string (if the service monitor command does not provide sufficient monitoring)|
|service.command.monitorcommand||Specifies a command that checks whether the service is running|
|service.port||Port where the service is running (for example, hue webserver runs on port 8888)|
To include a link to a user interface associated with this service in the MCS, enter a Uniform Resource Identifier (URI) in this property and also specify the port in the
|service.ui.port||If you want to include a link to the user interface associated with this service in the MCS, enter the port in this property and also specify the URI in the |
|service.logs.location||Location of the service log files|
|service.depends.local||Indicates whether service depends on a service instance locally, or on the master. Values = 1 (local) or 0 (master).|
|Specifies the abbreviated alarm name for this service. This is the alarm name that appears in the MCS. Once the service has been started by Warden, you cannot edit this value.|
|service.alarm.label||Specifies the alarm name for this service. This is the alarm name that appears in the |
|service.heapsize.percent||Specifies heapsize percent.|
|service.heapsize.max||Maximum heapsize in MB.|
|service.heapsize.min||Minimum heapsize in MB.|
|service.env||Specifies environment variables to be use by the service. By default, it may include "MAPR_MAPREDUCE_MODE=default". You can include a comma-separated list of environment variables within quotes. For example, service.env="MAPR_MAPREDUCE_MODE=default,ABC=1,XYZ=2"|
For more information about the MAPR_MAPREDUCE_MODE, see Managing the MapReduce Mode for Ecosystem Components.
Memory Management for Services
The following memory parameters are used to reserve memory for the service:
service.<servicename>.heapsize.percentparameter controls the percentage of system memory allocated to the named service.
service.<servicename>.heapsize.maxparameter defines the maximum heapsize used when invoking the service.
service.<servicename>.heapsize.minparameter defines the minimum heapsize used when invoking the service.
For example, the
service.command.gateway.heapsize.min parameters in the
warden.gateway.conf file controls the amount of memory that Warden allocates to the gateway service before allocating memory to other services.
The actual heap size used when invoking a service is a combination of the three parameters according to the formula
max(heapsize.min, min(heapsize.max, total-memory * heapsize.percent / 100)).
The hiveserver2 configuration file,
warden.hs2.conf, looks like this:
hiveserver2 is installed, the
warden.hs2.conf file is placed in the directory
/opt/mapr/conf/conf.d. If Warden is running, it will detect the file and start the service. If Warden is not running, the file is picked up when Warden starts. Warden monitors the service and displays the status on the MapR Control System UI.