Parameter Name | Default Value | Version Introduced | Description |
---|---|---|---|
|
| 6.8.0 | If greater than 0, ensures that has values are time bucketed every x days. Therefore, generating hash of an identical value x days apart will result in different hash values. |
|
| Semicolon-separated list of local directories scanned for system artifacts to add to the artifact repository. | |
|
| 6.6.0 | Maximum parallelism of system artifact loading. This can be a resource-consuming process, e.g. with repository on GCS upload can use 64MB buffer, so we need to ensure app fabric is not overwhelmed during the process. |
|
| App Fabric service bind port; if 0, binds to a random port. | |
|
| Directory where all archives are stored. | |
|
| Additional Java classpath for CDAP programs. These extra classpaths must be present on all nodes in the cluster. Supports wildcard suffix "*" to include all JAR files under a directory. | |
|
| Java options for all Apache Twill containers. | |
|
| Maximum number of concurrent program runs allowed; set to -1 for unlimited. Program runs are those with an active run record. | |
|
| 6.6.0 | Maximum number of concurrent launching runs allowed; set to -1 for unlimited. Launching runs have an active run record with PENDING or STARTING status. |
|
| Maximum amount of time (in seconds) in which a run record is retained in run record monitor. This is to safe guard launch requests flow-control such that if a request is somehow stuck in PENDING/STARTING state, it will be dropped from after the threshold. Note that | |
|
| Cleanup interval (in seconds) in which run record monitor service cleanup logic runs to delete old entries. Note that | |
|
| Size of the thread pool for launching programs | |
|
| Maximum number of seconds to wait for a program to start before killing it. | |
|
| Maximum number of seconds to wait for a program to stop before killing it. | |
|
| Interval in seconds of how often the run id corrector thread will run; this value should be greater than 0. | |
|
| Number of run records being fetched per transaction for checking if needed for correction. This value is directly proportional to the | |
|
| Interval in seconds for initial delay for the local dataset deletion thread; this value should be greater than 0. | |
|
| Interval in seconds of how often the local dataset deletion thread will run; this value should be greater than 0. | |
|
| Semicolon-separated list of local directories that are scanned for program runtime extensions. | |
|
| Enables Spark event logs collection. | |
|
| When | |
|
| Specify whether to rewrite the YARN 'Client.scala' class in Spark to work around issue SPARK-13441 in CDH clusters. | |
|
| Maximum number of events to fetch from the messaging system in each processing cycle for program status update events. | |
|
| The delay in milliseconds to check again for new program status events after it detects there was no event. | |
|
| The interval in milliseconds for the time window used by YARN Resource Manager to check for application max failure attempts. By default, this is only used for long running program, but can be override through runtime argument | |
|
| Defines how transactions are controlled for program methods invocation; "implicit" means that the platform encloses method execution into a transaction, whereas "explicit" means that the method itself is in control of executing transactions. | |
|
| Temp directory. | |
|
| Scheduler queue for CDAP programs and CDAP Explore queries. | |
|
| If true, redeploying an application will modify any schedules that currently exist for the application; if false, redeploying an application does not create any new schedules and existing schedules are neither deleted nor updated. This property only affects the redeployment of an application; all related actions or endpoints are unaffected. | |
|
| Bind address for app fabric service and dataset service. | |
|
| Additional jars to be localized to every program container and to be added to classpaths of CDAP programs. They can be local file paths on the CDAP Master or URIs of remote files. Multiple JAR files are comma- separated. | |
|
| Number of partitions in the scheduler's job queue. This is the same as the number of constraint checker threads started by the scheduler. | |
|
| Size of the scheduler thread pool. | |
|
| The number of milliseconds by which a schedule execution can miss its next-fire-time and still run. | |
|
| The delay in milliseconds that the scheduler checks again for new events after it detects there was no event. | |
|
| Maximum number of events to fetch from the messaging system in each processing cycle for time schedule events. | |
|
| Maximum number of events to fetch from the messaging system in each processing cycle for stream size schedule events. | |
|
| Maximum number of events to fetch from the messaging system in each processing cycle for data schedule events. | |
|
| Maximum number of events to fetch from the messaging system in each processing cycle for program status schedule events. | |
|
| Topic name for publishing time events from time scheduler to the messaging system. | |
|
| Topic name for publishing status transitioning events of program runs to the messaging system. | |
|
| Topic name for publishing program status recording events to the messaging system. | |
|
| Maximum allowed size in megabytes of a workflow token; if the workflow token exceeds this size, no further updates are allowed. | |
|
| Comma separated list of plugin dataset type requirements that cannot be met in the instance. Plugins that require any of these will be treated as if they don't exist. For example, if 'table' is given, any plugin that requires 'table' will be treated as if they don't exist. | |
|
| File containing the theme to be used in UI. |
Page Comparison
Manage space
Manage content
Integrations