blob: 4703cc0be6e4472ee8e1d83f8a1a2c855eb6537b [file] [log] [blame]
Ian Maxond8857792015-09-11 14:19:53 -07001 ~~ Licensed to the Apache Software Foundation (ASF) under one
2 ~~ or more contributor license agreements. See the NOTICE file
3 ~~ distributed with this work for additional information
4 ~~ regarding copyright ownership. The ASF licenses this file
5 ~~ to you under the Apache License, Version 2.0 (the
6 ~~ "License"); you may not use this file except in compliance
7 ~~ with the License. You may obtain a copy of the License at
8 ~~
9 ~~ http://www.apache.org/licenses/LICENSE-2.0
10 ~~
11 ~~ Unless required by applicable law or agreed to in writing,
12 ~~ software distributed under the License is distributed on an
13 ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
14 ~~ KIND, either express or implied. See the License for the
15 ~~ specific language governing permissions and limitations
16 ~~ under the License.
Ian Maxon137fc3b2015-06-30 16:23:48 -070017
vinayakb0c860392012-10-06 18:47:20 +000018Hyracks Overview
19
20 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
21 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
22 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
23 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
24 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
25 to facilitate testing.
26
27 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
28 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
29 chapter "Hyracks Concepts".