DSG stores cluster-wide options for DSE Graph in
dse.yaml under the
Most of the options that are common to modify have been discussed in the sections below.
Of particular note, the Graph sandbox is configured in the Gremlin Server options of the
This feature is enabled by default and provides protection from malicious attacks within the JVM.
dse.yaml settings, modify the file on each node in the cluster and restart each node.
Settings in the
dse.yaml are node system level in scope.
dse.yaml files can also be modified using OpsCenter.
The remote.yaml file is the primary configuration file for DSG Gremlin console connections to the Gremlin Server. Most options are self-explanatory. In particular, be aware that if you are using analytic OLAP queries with DSG, changes are required in this file.
The replication factor (RF) for a graph can affect the performance of reads and writes in DSG. Just as for the DSE database, these factors control the number of replicas of data that the distributed graph database will store across multiple nodes.
Consistency level in DSG is controlled with graph traversal options and used for read and write operations on a traversal basis.
Gremlin queries execute CQL commands to insert, read, and update graph data via traversals, and so the DSE database consistency level settings can affect the execution of graph operations.
The consistency level for reads or writes are set per graph with the
with('consistency', <cl_level>)used for both reads and writes.