Messaging System parameters (cdap-site.xml and cdap-default.xml)

messaging.cache.size.mb

30

Memory in megabytes for the cache size used by the messaging service for caching recently-published messages. Currently, only topics listed in the ${messaging.system.topics} configuration have caching enabled. Set it to 0 to disable caching.

messaging.container.instances

1

Number of instances for the messaging service.

messaging.container.memory.mb

${master.service.memory.mb}

Memory in megabytes for each messaging service instance.

messaging.container.num.cores

${master.service.num.cores}

Number of virtual cores for each messaging service instance.

messaging.coprocessor.metadata.cache.expiration.seconds

120

Number of seconds after which the metadata cache in HBase data table coprocessors will expire.

messaging.ha.fencing.delay.seconds

5

Number of seconds to wait before the leader process start serving requests.

messaging.hbase.max.scan.threads

96

Maximum number of threads used for scanning HBase tables.

messaging.hbase.scan.cache.rows

1000

Number of rows for caching that will be passed to HBase scanners. Higher caching values will enable faster scanning but will use more memory.

messaging.http.compress.payload

true

Compress payload for HTTP calls in the messaging system.

messaging.http.server.bind.address

0.0.0.0

Messaging HTTP server bind address.

messaging.http.server.bind.port

0

Messaging HTTP service bind port; if 0, binds to a random port.

messaging.http.server.consume.chunk.size

60000

Approximate size in bytes of each chunk streamed back to a consumer.

messaging.http.server.executor.threads

0

Number of executor threads for the HTTP server in the messaging system. If set to 0, no executor threads will be used and requests will be handled directly in the IO thread.

messaging.http.server.max.request.size.mb

10

Maximum request content size in megabytes for each request to the HTTP server in the messaging system.

messaging.http.server.worker.threads

30

Number of IO threads used by the HTTP server in the messaging system.

messaging.local.data.cleanup.frequency.secs

3600

Scheduling frequency of time-to-live cleanup thread in seconds (only used in CDAP Local Sandbox).

messaging.local.data.dir

${local.data.dir}/messaging

Local storage directory for the messaging system (used only in CDAP Local Sandbox).

messaging.max.instances [Final]

${master.service.max.instances}

Maximum number of instances for the messaging service. Increasing the number of messaging service instances only improves availability, but not scalability.

messaging.message.table.hbase.splits

16

Number of splits to use for the message table in HBase upon table creation.

messaging.message.table.name

tms.message

Name of the message table of the messaging system.

messaging.metadata.table.name

tms.meta

Name of the metadata table of the messaging system.

messaging.payload.table.hbase.splits

16

Number of splits to use for the payload table in HBase upon table creation.

messaging.payload.table.name

tms.payload

Name of the payload table of the messaging system.

messaging.system.topics [Final]

${audit.topic},

${metadata.messaging.topic},

${data.event.topic},

${metrics.topic.prefix}:${metrics.

messaging.topic.num},

${metrics.admin.topic},

${time.event.topic},

${program.status.event.topic},

${program.status.record.event.topic},

${log.tms.topic.prefix}:${log.publish.

num.partitions}

A comma-separated list of topics that are always available in the system namespace. Multiple topics sharing the same prefix and distinguished by different numerical suffixes can be specified with the syntax <common.prefix>:<total.topic.number>, where the <total.topic.number> is the total number of topics sharing the <common.prefix>, and the numerical suffixes will range from 0 to (<total.topic.number> - 1).

messaging.table.expiration.seconds

300

Number of seconds after which the messaging table cache will expire.

messaging.table.hbase.split.policy

org.apache.hadoop.hbase.regionserver.DisabledRegionSplitPolicy

The class name that controls the HBase table region split policy. Ideally, auto-splitting should be disabled for HBase tables used by the messaging system.

messaging.topic.default.ttl.seconds

604800

The default time-to-live in seconds for messages in a topic.

messaging.twill.java.heap.memory.ratio

0.6

The minimum ratio of heap to non-heap memory for the messaging service container.

messaging.twill.java.reserved.memory.mb

512

Desired reserved non-heap memory in megabytes for the messaging service container. The actual value is bounded by the ${twill.java.heap.memory.ratio} setting of the container memory size.