Configuration properties that can be modified

The table below describes the properties in $BDD_HOME/BDD_manager/conf/bdd.conf that you can modify. Be sure to read this information carefully before making changes to bdd.conf. Don't update any other properties in this file, as this could have negative effects on your cluster.

Property Description
AGENT_OUT_FILE The path to the HDFS Agent's stdout/stderr file.
BACKUP_HDFS_TEMP_FOLDER_PATH The absolute path to the default temporary folder on the Admin Server used during backup and restore operations. Note that this can also be overridden on a case-by-case basis by the bdd-admin script.
BACKUP_LOCAL_TEMP_FOLDER_PATH The absolute path to the default temporary folder on HDFS used during backup and restore operations. Note that this can also be overridden on a case-by-case basis by the bdd-admin script.
CLUSTERING_SERVICE_* These properties can't be modified directly. For information on enabling and disabling the Clustering Service, see enable-components and disable-components.
COMPANY_SECURITY_* These properties can't be modified directly. For information on updating user authentication settings, see Configuring authentication settings for users.
DETECTOR_* Hive Table Detector properties shouldn't be modified directly, although you can change the Detector's behavior by editing its cron job. For more information, see the Data Processing Guide.
DGRAPH_ADDITIONAL_ARG Defines one or more flags to start the Dgraph with. This property is only intended for use by Oracle Support.

Note that you cannot include flags that map to properties in bdd.conf. For more information on Dgraph flags, see Dgraph flags.

DGRAPH_CACHE The Dgraph cache size, in MB. For enhanced performance, Oracle recommends allocating at least 50% of the node's available RAM to the Dgraph cache. If you later find that queries are getting cancelled because there is not enough available memory to process them, you should increase this amount.
DGRAPH_CGROUP_NAME, DGRAPH_ENABLE_CGROUP Can be edited in certain circumstances. For instructions, see Setting up cgroups for the Dgraph.
DGRAPH_HDFS_MOUNT_DIR Can be edited in certain circumstances. For instructions, see Moving the Dgraph databases to HDFS.
DGRAPH_INDEX_DIR The path to the Dgraph databases directory. You must prepare the database files in the new location before changing the value of this property. See Moving the Dgraph databases to HDFS.
DGRAPH_LOG_LEVEL Optional. Defines the log levels for the Dgraph's out log subsystems. This must be formatted as: 
subsystem1 level1|subsystem2,subsystem3
						level2|subsystemN levelN
For example: 
DGRAPH_LOG_LEVEL=bulk_ingest WARNING|cluster ERROR|dgraph, eql, eve INCIDENT_ERROR

You can include as many subsystems as you want. Any you don't include will be set to NOTIFICATION. If you enter an unsupported or improperly formatted value, it will default to NOTIFICATION.

For more information on the Dgraph's out log subsystems and their supported levels, see Dgraph out log.

DGRAPH_OUT_FILE The path to the Dgraph's stdout/stderr file.
DGRAPH_SERVERS Can be edited in certain circumstances. For instructions, see Adding new Dgraph nodes and Moving the Dgraph databases to HDFS.
DGRAPH_THREADS The number of threads the Dgraph starts with. Oracle recommends the following:
  • For machines running only the Dgraph, the number of threads should be equal to the number of CPU cores on the machine.
  • For machines running the Dgraph and other BDD components, the number of threads should be the number of CPU cores minus 2. For example, a machine with 4 cores should have 2 threads.

Be sure that the number you use is in compliance with the licensing agreement.

DGRAPH_USE_MOUNT_HDFS Can be edited in certain circumstances. For instructions, see Moving the Dgraph databases to HDFS.
DGRAPH_USE_NFS_MOUNT Can be edited in certain circumstances. For instructions, see Moving the Dgraph databases to HDFS.
DP_ADDITIONAL_JARS Defines custom SerDe JARs to be added to Data Processing workflows. For more information, see the Data Processing Guide.
ENABLE_AUTOSTART Shouldn't be modified directly. For information on enabling autostart for components, see autostart.
ENABLE_CLUSTERING_SERVICE These properties can't be modified directly. For information on enabling and disabling the Clustering Service, see enable-components and disable-components.
ENABLE_ENRICHMENTS See the Data Processing Guide.
ENABLE_HIVE_TABLE_DETECTOR Shouldn't be modified after install time. For information on modifying the Hive Table Detector's behavior, see the Data Processing Guide.
ENABLE_KERBEROS Can be edited in certain circumstances. For instructions, see Enabling Kerberos.
ENDECA_SERVER_LOG_LEVEL For instructions on setting Dgraph Gateway log levels, see Setting the Dgraph Gateway log level.
HADOOP_CERTIFICATES_PATH Shouldn't be modified directly. See Refreshing TLS/SSL certificates.
HADOOP_CLIENT_LIB_PATHS Shouldn't be modified directly. See Updating the Hadoop client configuration files.
HIVE_DATABASE_NAME Can't be modified directly. If you want to change the database used by the Hive Table Detector, you must modify its cron job. For more information, see the Data Processing Guide.
HUE_URI Shouldn't be modified directly. See Setting the Hue URI.
JAVA_HOME The JDK used when starting the BDD components. If you change this value, you must also update the location used by the CLI and Studio. Note that this must be in the same location on all nodes in the cluster.
KERBEROS_KEYTAB_PATH Shouldn't be modified directly. See Updating the Kerberos keytab file.
KERBEROS_PRINCIPAL Shouldn't be modified directly. See Updating the Kerberos principal.
KERBEROS_TICKET_LIFETIME The amount of time that the Dgraph's Kerberos ticket is valid. This should be given as a number followed by a supported unit of time: s, m, h, or d. For example, 10h (10 hours), or 10m (10 minutes).
KERBEROS_TICKET_REFRESH_ INTERVAL The interval (in minutes) at which the Dgraph's Kerberos ticket is refreshed. For example, if set to 60, the Dgraph's ticket would be refreshed every 60 minutes, or every hour.
KRB5_CONF_PATH Shouldn't be modified directly. See Changing the location of the Kerberos krb5.conf file.
LANGUAGE For information on changing the language used by Data Processing, see the Data Processing Guide.
LDAP_* For instructions on configuring an LDAP for Studio, see Integrating with an LDAP System to Manage Users.
MAX_INPUT_SPLIT_SIZE See the Data Processing Guide.
MAX_RECORDS See the Data Processing Guide.
RECORD_SEARCH_THRESHHOLD See the Data Processing Guide.
STUDIO_ADMIN_* Shouldn't be modified directly. See Editing a Studio user.
STUDIO_JDBC_CACHE For instructions on enabling and disabling database caching for Studio, see the Installation Guide.
VALUE_SEARCH_THRESHHOLD See the Data Processing Guide.