Logging parameters (cdap-site.xml and cdap-default.xml)
- Robin Rielley
Parameter Name | Default Value | Description |
|---|---|---|
|
| In Distributed CDAP, the HDFS directory under which the system log pipeline saves log files. |
|
| Base directory for logs buffer. |
|
| Maximum size in bytes of a log buffer file. |
|
| Log buffer HTTP service bind address. |
|
| Log buffer HTTP service bind port. |
|
| Directory for log appender jars. |
| Â | Provider for log appender. The log appender provided by this provider will be loaded in each program container. |
|
| Comma-separated list of provisioners to enable log appender provider for program executions. |
|
| Log buffer recovery batch size in number of log events read. This will be used to recover logs in batches from log buffer upon log service restart. |
|
| Kafka topic name used to publish logs. |
|
| TMS topic prefix used to publish logs. |
|
| The buffer size used in Log Appender. |
|
| Permissions used by the system log pipeline when creating directories. |
|
| Time in minutes between runs of the log cleanup thread. |
|
| Batch size to clean up log metadata table. |
|
| Maximum time span in milliseconds of a log file created by the system log pipeline. |
|
| Maximum size in bytes of a log file created by the system log pipeline. |
|
| Permissions used by the system log pipeline when creating files. |
|
| Time in days a log file is retained. |
|
| Number of bytes for the sync interval setting of the Avro file written by the system log pipeline. |
|
| The ratio of total memory used for determining processing pipeline buffer size. This property is only used if |
|
| The internal buffer size in bytes for each log processing pipeline. Setting it to zero means the system will determine it dynamically based on the container size as given by |
|
| The time between log processing pipeline checkpoints in milliseconds. |
|
| A local directory on the CDAP Master that is scanned for log processing pipeline configurations. Each pipeline is defined by a file in the logback XML format, with ".xml" as the file name extension. |
|
| The time a log event stays in the log processing pipeline buffer before writing out to log appenders in milliseconds. A longer delay will result in better time ordering of log events before presenting to log appenders but will consume more memory. |
|
| The buffer size in bytes, per topic partition, for fetching log events from Kafka. |
|
| Comma-separated list of local directories on the CDAP Master scanned for additional library JAR files to be included for log processing. |
|
| Logger cache entry expiration time in milliseconds |
|
| The number of loggers that each log processing pipeline will cache. |
|
| Number of CDAP Kafka service partitions to publish the logs to. |
|
| Publish logs from an application or a program to the same partition. Valid values are "application" or "program". If set to "application", logs from all the programs of an application go to the same partition. If set to "program", logs from the same program go to the same partition. Changes to this property requires restarting of all CDAP applications. |
|
| Log query HTTP service bind address. |
|
| Log query HTTP service bind port. |
|
| Memory in megabytes for each log saver instance to run in YARN. |
|
| Number of virtual cores for each log saver instance in YARN. |
|
| Maximum number of log saver instances to run in YARN. |
|
| Number of log saver instances to run in YARN. |
|
| Log saver HTTP service bind address. |
Created in 2020 by Google Inc.