blob: f35b7e4de8c43a003aef552e3553b718cd6a84b9 [file] [log] [blame]
vinayakba955f162011-01-01 07:51:18 +00001Hyracks Overview
vinayakbf25a8332010-12-22 11:20:30 +00002
3 Hyracks employs a client-server architecture. On the server side, the software module that is responsible for interacting with clients, keeping track of and dispatching work
4 to other machines in the cluster is called the Hyracks Cluster Controller (CC). There is one CC per logical Hyracks cluster. The module that executes on the worker machine
5 and interacts with the CC to receive work and act on it, is called the Hyracks Node Controller (NC). Every NC in a single Hyracks cluster has a unique logical name. When an
6 NC is started, it is provided the address of the CC whose cluster it must join. Although it is sufficient to run one instance of the NC on a physical machine, it is possible
7 to run multiple instances of NCs (ofcourse each NC has a different logical name) on the same physical machine -- often used for simulating a cluster on a single machine
8 to facilitate testing.
9
10 Hyracks clients interact solely with the CC when submitting their jobs. A Hyracks Job is the unit of work that a client can execute on the Hyracks cluster. A job is expressed
11 as a directed acyclic graph (DAG) of Operators connected to each other by means of Connectors. A more detailed description of jobs, operators, and connectors follows in
vinayakba955f162011-01-01 07:51:18 +000012 chapter "Hyracks Concepts".