Master parameters (cdap-site.xml and cdap-default.xml)

hbase.client.retries.number

2

Maximum number of retries while performing HBase operations from master services.

hbase.rpc.timeout

15000

RPC timeout from HBase operations performed from master services.

hbase.version.resolution.strategy

auto.strict

Determines how to behave when the HBase version on a cluster is an unsupported value. The default value of "auto.strict" will require that the HBase version match a supported value, and CDAP Master will not start if the HBase version is unsupported. Set to "auto.latest" to use the latest HBase version available on the cluster with an unsupported HBase version.

http.service.boss.threads

1

Number of Netty service boss threads for master HTTP services.

http.service.connection.backlog

20000

Maximum connection backlog of master HTTP service.

http.service.exec.threads

20

Number of Netty service executor threads for master HTTP services.

http.service.worker.threads

10

Number of Netty service worker threads for master HTTP services.

master.collect.app.containers.log.level

ERROR

The log level of application container logs that are streamed back to the CDAP Master process log. The levels supported are "ALL", "TRACE", "DEBUG", "INFO", "WARN", "ERROR", and "OFF".

master.collect.containers.log

true

Determines if master service container logs are streamed back to the CDAP Master process log.

master.service.max.instances

5

Maximum number of master service instances

master.service.memory.mb

1024

Macro property to set the default memory in megabytes for each CDAP system container.

master.service.num.cores

2

Number of virtual cores for each master service instance.

master.services.scheduler.queue

Scheduler queue for CDAP Master services.

master.startup.service.timeout.seconds

600

Timeout in seconds for master services to wait for their dependent services to be available. For example, the dataset executor master service requires the transaction service, and will wait for the transaction service to become available while it is starting up. If the timeout is hit, the service will fail to start and the master service will shut itself down. If set to 0 or below, master services will not wait for their dependent services to start before starting themselves.