The Cluster Coordinator service uses a configuration file to specify its settings.
After the installation of the Cluster Coordinator, the configuration file is placed in the Oracle\Endeca\ClusterCoordinator\<version>\conf directory. When you run the clusterCoordinator script, it detects the configuration file.
# The number of milliseconds of each tick tickTime=2000 # The number of ticks that the initial # synchronization phase can take initLimit=10 # The number of ticks that can pass between # sending a request and getting an acknowledgment syncLimit=5 # the directory where the Cluster Coordinator snapshot is stored. dataDir=. # the port at which the clients will connect clientPort=2181Where:
Entry | Description |
---|---|
tickTime | The basic time unit in milliseconds used
by the Cluster Coordinator. It is used for heartbeats.
For example, tickTime can be 2000 milliseconds. The minimum session timeout is twice the tickTime. |
initLimit | The number of ticks that the initial
synchronization phase can take.
This number specifies the length of time the nodes have to connect to the leader node. |
syncLimit | The number of ticks that can take place between one node sending a request for an update and receiving an acknowledgment from the leader node. |
dataDir | The directory where the in-memory
database snapshots for the Cluster Coordinator and the transaction log of
updates to its database are stored.
This directory is created in the same file system location from which you run the Cluster Coordinator script. You can specify to store the log of updates to the database in another directory, using the log4j file stored in the /conf directory of the Cluster Coordinator installation. |
clientPort | The port at which clients should connect
to the Cluster Coordinator service.
As configured after the initial installation, this port is 2181. |