Data Hub Local Locks Strategy

Use Local Locks Strategy in a clustered environment to achieve better performance during concurrent writes. When using this strategy you can write only to the master node; you cannot write to non-master nodes.
Note: Scheduled backups are not supported with Local Locks Strategy.
  1. Ensure the cluster is running.
  2. Open a web browser and go to the master node location for the following:

    http://serverName:8080/jmx-console/HubEngineSettings MBean

  3. Set UseLocalLockFactory to true. In the wrapper.log file you will see the following:
    [GraphEngineSettingsManager] Switching to Local-Only locking strategy. SERVER/CLUSTER RESTART REQUIRED.
  4. Shut down all nodes in the cluster.
  5. On each non-master node, add the following two properties to the <Spectrumâ„¢ Technology Platform install path>/server/modules/hub/db/neo4j.properties file:
    #Whether this instance should only participate as slave in cluster. If set to true, it will never be elected as master.
    ha.slave_only=true
    dbms.read_only=true
  6. Save the file.
  7. Restart the cluster. Make sure the master node points to itself when starting the cluster backup for the first time. After restart, you should see in the wrapper.log:
    WARN [GraphEngineFactory]
    ===============================================================================
    Using Local-Only locking strategy. Must set read_only=true in neo4j.properties
    on all servers except master.
    ===============================================================================