Go to file
Wang, Fei e9bc6792a7 [KYUUBI #6997] Get the latest batch app info after submit process terminated to prevent batch ERROR due to engine submit timeout
### Why are the changes needed?

We meet below issue:
For spark on yarn:
```
spark.yarn.submit.waitAppCompletion=false
kyuubi.engine.yarn.submit.timeout=PT10M
```

Due to network issue, the application submission was very slow.

It was submitted after 15 minutes.
<img width="1430" alt="image" src="https://github.com/user-attachments/assets/a326c3d1-4d39-42da-b6aa-cad5f8e7fc4b" />

<img width="1350" alt="image" src="https://github.com/user-attachments/assets/8e20056a-bd71-4515-a5e3-f881509a34b2" />

Then the batch failed from PENDING state to ERRO state directly, due to application state NOT_FOUND(exceeds the kyuubi.engine.yarn.submit.timeout).

a54ee39ab3/kyuubi-server/src/main/scala/org/apache/kyuubi/engine/ApplicationOperation.scala (L99-L106)

<img width="1727" alt="image" src="https://github.com/user-attachments/assets/20a2987c-675c-4136-a107-001f30b1b217" />

Here is the operation event:
<img width="1727" alt="image" src="https://github.com/user-attachments/assets/e2bab9c3-a959-4e2b-a207-813ae6489b30" />

But from the batch log, the current application status should be `PENDING`.
```
:2025-03-21 17:36:19.350 INFO [KyuubiSessionManager-exec-pool: Thread-176922] org.apache.kyuubi.operation.BatchJobSubmission: Batch report for bbba09c8-3704-4a87-8394-9bcbbd39cc34, Some(ApplicationInfo(application_1741747369441_2258235,6042072c-e8fa-425d-a6a3-3d5bbb4ec1e3-275732_6042072c-e8fa-425d-a6a3-3d5bbb4ec1e3-275732.e3a34b86-7fc7-43ea-b4a5-1b6f27df54b5.0_20250322002147.stm,PENDING,Some(https://apollo-rno-rm-2.vip.hadoop.ebay.com:50030/proxy/application_1741747369441_2258235/),Some()))
```

So, we should retrieve the batch application info after the submission process terminated before checking the application failed, to get the current application information to prevent the corner case:
1. the application submission time exceeds the `kyuubi.engine.yarn.submit.timeout` and the app state is NOT FOUND
2. can not get the application report before the submission process terminated
3. then the batch state to ERROR from PENDING directly.

Conclusion:

The application state transition was:

UNKNOWN(before submit timeout) -> NOT_FOUND(reach submit timeout) -> processExit -> batchOpError -> PENDING(updateApplicationInfoMetadataIfNeeded) -> UNKNOWN(batchError but app not terminated)

After this PR, it should be:

UNKNOWN(before submit timeout) -> NOT_FOUND(reach submit timeout) ->  processExit-> PENDING(after process terminated) -> ....

### How was this patch tested?

Existing GA.

### Was this patch authored or co-authored using generative AI tooling?

No.

Closes #6997 from turboFei/app_not_found_v2.

Closes #6997

370cf49e9 [Wang, Fei] v2
912ec28ca [Wang, Fei] nit
3c376f922 [Wang, Fei] log the op ex
d9cbdb87d [Wang, Fei] fix app not found

Authored-by: Wang, Fei <fwang12@ebay.com>
Signed-off-by: Wang, Fei <fwang12@ebay.com>
(cherry picked from commit 196b47e32a)
Signed-off-by: Wang, Fei <fwang12@ebay.com>
2025-03-24 12:53:35 -07:00
.github [KYUUBI #6837] [INFRA] Disable K8s CI image GHA cache 2024-12-04 20:34:19 +08:00
.idea
bin [KYUUBI #6609] Bump Spark 3.5.2 2024-08-14 21:00:30 +08:00
build [KYUUBI #6757] Pass build args to extra spark engine build command 2024-10-21 10:03:19 +08:00
charts/kyuubi [KYUUBI #6620] [K8S][HELM] Update default Kyuubi version to 1.9.2 2024-08-16 10:57:33 +00:00
conf [KYUUBI #6268] Specify logDir for RollingFile filePattern 2024-04-09 17:32:29 +08:00
dev [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
docker [KYUUBI #6080] Improve instruction for deploy Kyuubi on K8s 2024-02-26 13:40:32 +08:00
docs [KYUUBI #6728] [DOC] update Authz plugin docs of build command with -am option 2024-10-16 13:31:41 +08:00
extensions [KYUUBI #6939] KSHC supports Spark 3.5.5 2025-03-03 14:03:32 +08:00
externals [KYUUBI #6984] Fix ValueError when rendering MapType data 2025-03-19 21:18:52 -07:00
integration-tests [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-assembly [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-common [KYUUBI #6997] Get the latest batch app info after submit process terminated to prevent batch ERROR due to engine submit timeout 2025-03-24 12:53:35 -07:00
kyuubi-ctl [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-events [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-ha [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-hive-beeline [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-hive-jdbc [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-hive-jdbc-shaded [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-metrics [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-rest-client [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-server [KYUUBI #6997] Get the latest batch app info after submit process terminated to prevent batch ERROR due to engine submit timeout 2025-03-24 12:53:35 -07:00
kyuubi-util [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-util-scala [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
kyuubi-zookeeper [RELEASE] Bump 1.9.4-SNAPSHOT 2024-11-29 06:26:52 +00:00
licenses
licenses-binary [KYUUBI #6392] Support javax.servlet and jakarta.servlet co-exist 2024-05-20 21:09:50 +08:00
.asf.yaml [KYUUBI #5342] Add label hacktoberfest to project 2023-09-28 12:13:16 +08:00
.dockerignore
.gitattributes [KYUUBI #5335] Set markdown file EOL 2023-09-27 22:02:09 +08:00
.gitignore [KYUUBI #6416] Generate flattened POM 2024-05-24 18:20:36 +08:00
.rat-excludes [KYUUBI #6109] Fork beeline module from Apache Hive 3.1.3 2024-03-11 11:26:39 +08:00
.readthedocs.yaml
.scalafmt.conf
codecov.yml [KYUUBI #5501] Update codecov token and fix codecov reporting on PRs 2023-10-26 14:57:36 +08:00
CONTRIBUTING.md [KYUUBI #6068] Remove community section from user docs 2024-02-21 05:20:42 +00:00
LICENSE [KYUUBI #5484] Remove legacy Web UI 2023-10-25 13:36:00 +08:00
LICENSE-binary [KYUUBI #6458] Remove commons-logging from binary release 2024-06-11 11:32:44 +08:00
NOTICE [KYUUBI #5953] [LICENSE] Update NOTICE 2024-01-10 19:29:01 +08:00
NOTICE-binary [KYUUBI #6458] Remove commons-logging from binary release 2024-06-11 11:32:44 +08:00
pom.xml [KYUUBI #6838] [INFRA] Update archive mailing list address 2024-12-04 23:35:25 +08:00
README.md [KYUUBI #5432] Fix typo in README.md 2023-10-16 22:03:57 +08:00
scalastyle-config.xml

Kyuubi logo

Project - Documentation - Who's using

Apache Kyuubi

Apache Kyuubi™ is a distributed and multi-tenant gateway to provide serverless SQL on data warehouses and lakehouses.

What is Kyuubi?

Kyuubi provides a pure SQL gateway through Thrift JDBC/ODBC interface for end-users to manipulate large-scale data with pre-programmed and extensible Spark SQL engines. This "out-of-the-box" model minimizes the barriers and costs for end-users to use Spark at the client side. At the server-side, Kyuubi server and engines' multi-tenant architecture provides the administrators a way to achieve computing resource isolation, data security, high availability, high client concurrency, etc.

  • A HiveServer2-like API
  • Multi-tenant Spark Support
  • Running Spark in a serverless way

Target Users

Kyuubi's goal is to make it easy and efficient for anyone to use Spark(maybe other engines soon) and facilitate users to handle big data like ordinary data. Here, anyone means that users do not need to have a Spark technical background but a human language, SQL only. Sometimes, SQL skills are unnecessary when integrating Kyuubi with Apache Superset, which supports rich visualizations and dashboards.

In typical big data production environments with Kyuubi, there should be system administrators and end-users.

  • System administrators: A small group consists of Spark experts responsible for Kyuubi deployment, configuration, and tuning.
  • End-users: Focus on business data of their own, not where it stores, how it computes.

Additionally, the Kyuubi community will continuously optimize the whole system with various features, such as History-Based Optimizer, Auto-tuning, Materialized View, SQL Dialects, Functions, etc.

Usage scenarios

Port workloads from HiveServer2 to Spark SQL

In typical big data production environments, especially secured ones, all bundled services manage access control lists to restricting access to authorized users. For example, Hadoop YARN divides compute resources into queues. With Queue ACLs, it can identify and control which users/groups can take actions on particular queues. Similarly, HDFS ACLs control access of HDFS files by providing a way to set different permissions for specific users/groups.

Apache Spark is a unified analytics engine for large-scale data processing. It provides a Distributed SQL Engine, a.k.a, the Spark Thrift Server(STS), designed to be seamlessly compatible with HiveServer2 and get even better performance.

HiveServer2 can identify and authenticate a caller, and then if the caller also has permissions for the YARN queue and HDFS files, it succeeds. Otherwise, it fails. However, on the one hand, STS is a single Spark application. The user and queue to which STS belongs are uniquely determined at startup. Consequently, STS cannot leverage cluster managers such as YARN and Kubernetes for resource isolation and sharing or control the access for callers by the single user inside the whole system. On the other hand, the Thrift Server is coupled in the Spark driver's JVM process. This coupled architecture puts a high risk on server stability and makes it unable to handle high client concurrency or apply high availability such as load balancing as it is stateful.

Kyuubi extends the use of STS in a multi-tenant model based on a unified interface and relies on the concept of multi-tenancy to interact with cluster managers to finally gain the ability of resources sharing/isolation and data security. The loosely coupled architecture of the Kyuubi server and engine dramatically improves the client concurrency and service stability of the service itself.

DataLake/Lakehouse Support

The vision of Kyuubi is to unify the portal and become an easy-to-use data lake management platform. Different kinds of workloads, such as ETL processing and BI analytics, can be supported by one platform, using one copy of data, with one SQL interface.

  • Logical View support via Kyuubi DataLake Metadata APIs
  • Multiple Catalogs support
  • SQL Standard Authorization support for DataLake(coming)

Cloud Native Support

Kyuubi can deploy its engines on different kinds of Cluster Managers, such as, Hadoop YARN, Kubernetes, etc.

The Kyuubi Ecosystem(present and future)

The figure below shows our vision for the Kyuubi Ecosystem. Some of them have been realized, some in development, and others would not be possible without your help.

Online Documentation Documentation Status

Quick Start

Ready? Getting Started with Kyuubi.

Contributing

Project & Community Status

Aside

The project took its name from a character of a popular Japanese manga - Naruto. The character is named Kyuubi Kitsune/Kurama, which is a nine-tailed fox in mythology. Kyuubi spread the power and spirit of fire, which is used here to represent the powerful Apache Spark. Its nine tails stand for end-to-end multi-tenancy support of this project.