formerly created Spark application for user ‘anonymous’ will not be reused in this case, while a brand new application will be submitted for user ‘kentyao’ instead. Then, you can see 3 processes running in server.ZooKeeperServer: Client attempting to establish new session at /127.0.0.1:65320 2021-01-16 03:27:35.455 INFO persistence.FileTxnLog: Creating new log file: log.1 2021-01-16 03:27:35.491 INFO server principal String keytab = args[1]; // keytab file location Configuration configuration = new Configuration(); configuration.set(HADOOP_SECURITY_AUTHENTICATION, "kerberos"); UserGroupInformation

formerly created Spark application for user ‘anonymous’ will not be reused in this case, while a brand new application will be submitted for user ‘kentyao’ instead. Then, you can see 3 processes running in server.ZooKeeperServer: Client attempting to establish new session at /127.0.0.1:65320 2021-01-16 03:27:35.455 INFO persistence.FileTxnLog: Creating new log file: log.1 2021-01-16 03:27:35.491 INFO server principal String keytab = args[1]; // keytab file location Configuration configuration = new Configuration(); configuration.set(HADOOP_SECURITY_AUTHENTICATION, "kerberos"); UserGroupInformation

for connection here is much shorter than the last round. If you use a different user to create a new connection, another engine will be started. $ bin/beeline -u 'jdbc:hive2://localhost:10009/' -n kentyao backend.engine.exec.pool.keepalive.time PT1M Time(ms) that an idle async thread of the operation for a new task to arrive before terminating in SQL e kyuubi.backend.engine.exec.pool.shutdown.timeout PT10S backend.server.exec.pool.keepalive.time PT1M Time(ms) that an idle async thread of the operation for a new task to arrive before terminating in Kyuu kyuubi.backend.server.exec.pool.shutdown.timeout PT10S Timeout(ms)

for connection here is much shorter than the last round. If you use a different user to create a new connection, another engine will be started. $ bin/beeline -u 'jdbc:hive2://localhost:10009/' -n kentyao backend.engine.exec.pool.keepalive.time PT1M Time(ms) that an idle async thread of the operation for a new task to arrive before terminating in SQL e kyuubi.backend.engine.exec.pool.shutdown.timeout PT10S backend.server.exec.pool.keepalive.time PT1M Time(ms) that an idle async thread of the operation for a new task to arrive before terminating in Kyuu kyuubi.backend.server.exec.pool.shutdown.timeout PT10S Timeout(ms)

for connection here is much shorter than the last round. If you use a different user to create a new connection, another engine will be started. This may change depending on the engine share level you time PT1M Time(ms) that an idle async thread of the operation execution thread pool will wait for a new task to arrive before terminating in SQL engine applications durat ion 1.0.0 kyuubi.backend.en gine time PT1M Time(ms) that an idle async thread of the operation execution thread pool will wait for a new task to arrive before terminating in Kyuubi server durat ion 1.0.0 kyuubi.backend.ser ver.exec.pool

for connection here is much shorter than the last round. If you use a different user to create a new connection, another engine will be started. This may change depending on the engine share level you time PT1M Time(ms) that an idle async thread of the operation execution thread pool will wait for a new task to arrive before terminating in SQL engine applications durat ion 1.0.0 kyuubi.backend.en gine time PT1M Time(ms) that an idle async thread of the operation execution thread pool will wait for a new task to arrive before terminating in Kyuubi server durat ion 1.0.0 kyuubi.backend.ser ver.exec.pool

for connection here is much shorter than the last round. If you use a different user to create a new connection, another engine will be started. $ bin/beeline -u 'jdbc:hive2://localhost:10009/' -n kentyao gracefully. We could delete a k.i. but not stop it immediately. In this case, the k.i. will not take any new connection request but only operation requests from existing connections. After all connection are stop until all session closed, and then you can start a new Kyuubi server. • If you use a random port for Kyuubi server You can just start the new Kyuubi Server, and then run cmd using bin/kyuubi-ctl:

for connection here is much shorter than the last round. If you use a different user to create a new connection, another engine will be started. $ bin/beeline -u 'jdbc:hive2://localhost:10009/' -n kentyao gracefully. We could delete a k.i. but not stop it immediately. In this case, the k.i. will not take any new connection request but only operation requests from existing connections. After all connection are stop until all session closed, and then you can start a new Kyuubi server. • If you use a random port for Kyuubi server You can just start the new Kyuubi Server, and then run cmd using bin/kyuubi-ctl:

for connection here is much shorter than the last round. If you use a different user to create a new connection, another engine will be started. $ bin/beeline -u 'jdbc:hive2://localhost:10009/' -n kentyao gracefully. We could delete a k.i. but not stop it immediately. In this case, the k.i. will not take any new connection request but only operation requests from existing connections. After all connection are stop until all session closed, and then you can start a new Kyuubi server. • If you use a random port for Kyuubi server You can just start the new Kyuubi Server, and then run cmd using bin/kyuubi-ctl:

for connection here is much shorter than the last round. If you use a different user to create a new connection, another engine will be started. $ bin/beeline -u 'jdbc:hive2://localhost:10009/' -n kentyao gracefully. We could delete a k.i. but not stop it immediately. In this case, the k.i. will not take any new connection request but only operation requests from existing connections. After all connection are stop until all session closed, and then you can start a new Kyuubi server. • If you use a random port for Kyuubi server You can just start the new Kyuubi Server, and then run cmd using bin/kyuubi-ctl: