Configuration properties that can be modified

You can modify some of the properties in bdd.conf before running the refresh-config command, but changing others could have negative effects on your cluster. For example, changing the value of ADMIN_SERVER would prevent Big Data Discovery from starting.

The table below describes the properties that can be modified. Be sure to read this information carefully before making changes. Do not make changes to any other properties in this file.

Note that the DGRAPH_* and AGENT_OUT_FILE parameters will be used when the bdd-admin script is run. This means that any changes will be applied for any Dgraph (and Dgraph HDFS Agent) that is subsequently restarted.

Property Description
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_OUT_FILE The path to the Dgraph's stdout/stderr file.
DGRAPH_INDEX_DIR The path to the Dgraph index on the NFS. This location contains the directory defined by DGRAPH_INDEX_NAME. You must prepare the index files on the NFS before changing the value of this property.
DGRAPH_INDEX_NAME The name of the Dgraph index, which is located in the directory defined by DGRAPH_INDEX_DIR. You must prepare the index files on the NFS before changing the value of this property.
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 amount size of the Dgraph cache, 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_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.