Summary of operations handled by the leader node and any node

This topic summarizes which specific requests to the Oracle Endeca Server should be directed to the leader node and which can be handled by any node.

Operations on the leader node only

These operations should be directed to the leader node only:
  • Updates to data records. If you are adding more records to the application, they should be sent to the Oracle Endeca Server that is hosting the leader node.

    This means that operations from the Data Ingest Web Service and the Bulk Load interface should be directed to the leader node only.

  • Snapshot operations from the Administrative Web Service. Operations for taking and applying a snapshot should be directed to the leader node only.
  • Updating operations from the Configuration Web Service. All requests to the Oracle Endeca Server that require changing schema for the records or the XML configuration documents should be directed to the leader node.
  • The rollBackOuterTransaction operation from the Transaction Web Service should be run on the leader node.
  • Administrative operations for the data store of the Oracle Endeca Server. The following administrative operations should be directed to the server that is hosting the Dgraph designated as the leader node:
    • /admin/datastore?op=merge
    • /admin/datastore?op=reload-services
    • /admin/datastore?op=updateaspell

Operations on any node

The following operations can be directed to any node in the cluster (including any of the follower nodes):
  • Any request from the Conversation Web Service (this means any request from Studio asking for read-only queries against the data).
  • Any request from the Administrative Web Service other than snapshot-related operations.
  • Any read-only request from the Configuration Web Service.
  • Some administrative operations for the Oracle Endeca Server. The following administrative operations can be directed to any node in the cluster:
    • /admin/datastore?op=flush
    • /admin/datastore?op=logroll
    • /admin/datastore?op=stats
    • /admin/datastore?op=statsreset