hi Diego the config "kylin.job.run.as.remote.cmd" is somehow ambiguous , it is enabled when you cannot run Kylin server on the same machine as your hadoop CLI, for example, if you're starting Kylin from you local IDE, and you hadoop CLI is a sandbox in another machine, this is the "remote" case.
In most of the production deployments we suggest using '"non-remote" mode, that is, kylin instance is started on the hadoop CLI. The picture depicts the scenario: https://github.com/apache/incubator-kylin/blob/0.7/website/images/install/on_cli_install_scene.png Kylin instances are stateless, the runtime state is saved in its "Metadata Store" in hbase (kylin.metadata.url config in conf/kylin.properties). For load balance considerations it is possible to start multiple Kylin instances sharing the same metadata store (thus sharing the same state on table schemas, job status, cube status, etc.) Each of the kylin instances has a kylin.server.mode entry in conf/kylin.properties specifying the runtime mode, it has three options: 1. "job" for running job engine only 2. "query" for running query engine only and 3 "all" for running both. Notice that only one server can run the job engine("all" mode or "job" mode), the others must all be "query" mode. A typical scenario is depicted in the attachment chart. -- Regards, *Bin Mahone | 马洪宾* Apache Kylin: http://kylin.io Github: https://github.com/binmahone
