logs: Where the logs of the Kyuubi server locates. • pid: stores the PID file of the Kyuubi server instance. • work: the root of the working directories of all the forked sub-processes, a.k.a. SQL engines \/___/ \/_/ /\___/ \/__/ If all goes well, this will result in the creation of the Kyuubi server instance with a PID stored in $KYUUBI_HOME/ pid/kyuubi--org.apache.kyuubi.server.KyuubiServer.pid instead. Then, you can see 3 processes running in your local environment, including one KyuubiServer instance and 2 SparkSubmit instances as the SQL engines. 16 Chapter 6. High Availability Kyuubi, Release

logs: Where the logs of the Kyuubi server locates. • pid: stores the PID file of the Kyuubi server instance. • work: the root of the working directories of all the forked sub-processes, a.k.a. SQL engines \/___/ \/_/ /\___/ \/__/ If all goes well, this will result in the creation of the Kyuubi server instance with a PID stored in $KYUUBI_HOME/ pid/kyuubi--org.apache.kyuubi.server.KyuubiServer.pid instead. Then, you can see 3 processes running in your local environment, including one KyuubiServer instance and 2 SparkSubmit instances as the SQL engines. 16 Chapter 6. High Availability Kyuubi, Release

logs: where the logs of the Kyuubi server locates. • pid: stores the PID file of the Kyuubi server instance. • work: the root of the working directories of all the forked sub-processes, a.k.a. SQL engines \/___/ \/_/ /\___/ \/__/ If all goes well, this will result in the creation of the Kyuubi server instance with a PID stored in $KYUUBI_HOME/ pid/kyuubi--org.apache.kyuubi.server.KyuubiServer.pid instead. Then, you can see 3 processes running in your local environment, including one KyuubiServer instance and 2 SparkSubmit instances as the SQL engines. 75730 Jps 70843 KyuubiServer 72566 SparkSubmit

logs: where the logs of the Kyuubi server locates. • pid: stores the PID file of the Kyuubi server instance. • work: the root of the working directories of all the forked sub-processes, a.k.a. SQL engines \/___/ \/_/ /\___/ \/__/ If all goes well, this will result in the creation of the Kyuubi server instance with a PID stored in $KYUUBI_HOME/ pid/kyuubi--org.apache.kyuubi.server.KyuubiServer.pid instead. Then, you can see 3 processes running in your local environment, including one KyuubiServer instance and 2 SparkSubmit instances as the SQL engines. 75730 Jps 70843 KyuubiServer 72566 SparkSubmit

logs: Where the logs of the Kyuubi server locates. pid: stores the PID file of the Kyuubi server instance. work: the root of the working directories of all the forked sub-processes, a.k.a. SQL engines. /\___/ \/__/ If all goes well, this will result in the creation of the Kyuubi server instance with a PID stored in $KYUUBI_HOME/pid/kyuubi-- org.apache.kyuubi.server.KyuubiServer.pid instead. Then, you can see 3 processes running in your local environment, including one KyuubiServer instance and 2 SparkSubmit instances as the SQL engines. 75730 Jps 70843 KyuubiServer 72566 SparkSubmit

logs: Where the logs of the Kyuubi server locates. pid: stores the PID file of the Kyuubi server instance. work: the root of the working directories of all the forked sub-processes, a.k.a. SQL engines. /\___/ \/__/ If all goes well, this will result in the creation of the Kyuubi server instance with a PID stored in $KYUUBI_HOME/pid/kyuubi-- org.apache.kyuubi.server.KyuubiServer.pid instead. Then, you can see 3 processes running in your local environment, including one KyuubiServer instance and 2 SparkSubmit instances as the SQL engines. 75730 Jps 70843 KyuubiServer 72566 SparkSubmit

logs: where the logs of the Kyuubi server locates. • pid: stores the PID file of the Kyuubi server instance. • work: the root of the working directories of all the forked sub-processes, a.k.a. SQL engines \/___/ \/_/ /\___/ \/__/ If all goes well, this will result in the creation of the Kyuubi server instance with a PID stored in $KYUUBI_HOME/pid/ kyuubi--org.apache.kyuubi.server.KyuubiServer.pid Then, you can see two processes running in your local environment, including one KyuubiServer instance, one SparkSubmit FlinkSQLEngine or TrinoSqlEngine instances as the SQL engines. • Spark 75730

logs: where the logs of the Kyuubi server locates. • pid: stores the PID file of the Kyuubi server instance. • work: the root of the working directories of all the forked sub-processes, a.k.a. SQL engines \/___/ \/_/ /\___/ \/__/ If all goes well, this will result in the creation of the Kyuubi server instance with a PID stored in $KYUUBI_HOME/pid/ kyuubi--org.apache.kyuubi.server.KyuubiServer.pid Then, you can see two processes running in your local environment, including one KyuubiServer instance, one SparkSubmit FlinkSQLEngine or TrinoSqlEngine instances as the SQL engines. • Spark 75730

logs: where the logs of the Kyuubi server locates. pid: stores the PID file of the Kyuubi server instance. work: the root of the working directories of all the forked sub-processes, a.k.a. SQL engines. /\___/ \/__/ If all goes well, this will result in the creation of the Kyuubi server instance with a PID stored in $KYUUBI_HOME/pid/kyuubi-- org.apache.kyuubi.server.KyuubiServer.pid instead. Then, you can see 3 processes running in your local environment, including one KyuubiServer instance and 2 SparkSubmit instances as the SQL engines. 75730 Jps 70843 KyuubiServer 72566 SparkSubmit

logs: where the logs of the Kyuubi server locates. pid: stores the PID file of the Kyuubi server instance. work: the root of the working directories of all the forked sub-processes, a.k.a. SQL engines. /\___/ \/__/ If all goes well, this will result in the creation of the Kyuubi server instance with a PID stored in $KYUUBI_HOME/pid/kyuubi-- org.apache.kyuubi.server.KyuubiServer.pid instead. Then, you can see 3 processes running in your local environment, including one KyuubiServer instance and 2 SparkSubmit instances as the SQL engines. 75730 Jps 70843 KyuubiServer 72566 SparkSubmit