Configuration properties that can be modified

The table below describes the properties in 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
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.
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.
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_CACHE The Dgraph cache size, in MB. There is no default value for this property, so you must provide one.

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_OUT_FILE The path to the Dgraph's stdout/stderr file.
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"
Be sure to include the quotes. 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_ADDITIONAL_ARG
Note: This property is only intended for use by Oracle Support.
Defines one or more flags to start the Dgraph with. Each flag must be quoted.

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

AGENT_OUT_FILE The path to the HDFS Agent's stdout/stderr file.