Setting Cloudera Director Properties

This topic lists the configuration properties recognized by Cloudera Director. Upon installation, these properties are pre-configured with reasonable default values, and you can run either client or server versions without specifying any of them. However, you might want to customize one or more properties, depending on your environment and the Cloudera Director features you want to use.

Setting Configuration Properties

The Cloudera Director command line provides the simplest way to specify a configuration property. For example:

./bin/cloudera-director bootstrap aws.simple.conf \
--lp.pipeline.retry.maxWaitBetweenAttempts=60
./bin/cloudera-director-server --lp.security.disabled=false

While the application.properties files are located on the Cloudera Director EC2 instance at /etc/cloudera-director-client/application.properties for the client, and /etc/cloudera-director-server/application.properties, you can see an example of the files on Cloudera's GitHub site, showing the configuration properties.

For users upgrading Cloudera Director

If you modified the application.properties file in Cloudera Director, the result of an upgrade depends on the version of Linux you are using:
  • RHEL and CentOS - When new properties are introduced in Cloudera Director, they are added to application.properties.rpmnew. The original application.properties file functions as before and is not overwritten with the new Cloudera Director version properties. You do not need to copy the new properties from application.properties.rpmnew to the old application.properties file.
  • Ubuntu - The modified Cloudera Director application.properties file is backed up to a file named application.properties.dpkg-old. The original application.properties file is then overwritten by the new application.properties file containing new Cloudera Director properties. After upgrading, copy your changes from application.properties.dpkg-old to the new application.properties file.

All the new properties are commented, and they all use valid defaults, so you do not necessarily need to merge the two properties files. But you must merge the two files if you want to modify one of the newly introduced properties.

Property Types

Type Description
boolean Either true or false
char Single character
directory Valid directory path
enum Fixed set of string values; a list of each enumeration’s values is provided following the main property table below
enum list Comma-separated list of enums
file Valid file path
int Integer (32-bit)
long Long integer (64-bit)
string Ordinary character string
time unit Enumeration of time units: DAYS, HOURS, MICROSECONDS, MILLISECONDS, MINUTES, NANOSECONDS, SECONDS