Distributed deployment

Cluster installation or distributed deployment of Hypertable for Windows requires manual configuration. Consider the following different setups.

Not using a shared or distributed file system

Usually a single node runs a complete Hypertable instance (DFS broker, Hyperspace, Master, Range Server and optionally the Thrift broker) with all participating nodes running only range servers. Instead of sharing the file system a single, system wide DFS broker will be shared by all participating nodes running the range servers. If possible the configuration of all of the participating nodes can be shared by using a simple network share. Note that the network share must be accessible for the user for which the Hypertable service is running. Assuming that the master node runs a complete Hypertable instance and uses the default ports, a sample configuration for the participating nodes is given below:

Each participating range server requires a unique location id which must be configured using

or

Using Windows Server DFS

If a DFS setup is used the master node runs a complete Hypertable instance (DFS broker, Hyperspace, Master, Range Server and optionally the Thrift broker) with all participating nodes running a range server and a DFS broker. Each DFS broker must be configured such that the root folders point to the same location. Assuming that the master node runs a complete Hypertable instance and uses the default ports, a sample configuration for the participating nodes is given below:

Note that the location configured by DfsBroker.Local.Root must be accessible for the user for which the Hypertable service is running. Depending on the DFS configuration, the Hypertable service must most likely run under a domain user account.

Collaborate with a heterogeneous cluster

Hypertable for Windows collaborates with Hypertable servers built for other platforms in a heterogeneous cluster.