[Feature][EnginePlugin] Enhance Hive engine concurrency capability
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- backend, databases, distributed-systems
Research direction
Begin in linkis-engineconn-plugins/hive and reproduce the reported behavior with 50+ concurrent Hive SQL jobs while monitoring queueing, delays, timeouts, and resource use. Profile the concurrency, connection-pool, scheduling, and resource-management paths before choosing a focused change. Done requires a defined concurrency improvement, overload handling, cleanup behavior, and high-concurrency performance coverage.
Written by the indexing model from the issue text.
Description
Linkis Component
linkis-engineconn-plugins/hive
What happened
English:
The current Hive engine has performance bottlenecks or stability issues in high-concurrency scenarios, unable to meet the needs of large-scale concurrent jobs.
Problem Description:
- Hive engine's concurrent processing capability is insufficient
- Job delays or failures may occur in high-concurrency scenarios
- Connection pool management needs optimization
中文:
当前Linkis的Hive引擎在高并发场景下存在性能瓶颈或稳定性问题,无法满足大规模并发作业的需求。
问题描述:
- Hive引擎并发处理能力不足
- 高并发场景下可能出现作业延迟或失败
- 连接池管理需要优化
What you expected to happen
English:
Users need to submit a large number of Hive jobs simultaneously on the Linkis platform, requiring the system to handle them stably and efficiently.
Expected Improvements:
- Increase maximum concurrent job limit per Hive EC
- Optimize connection pool size and lifecycle management
- Improve job queue and scheduling mechanism
- Add backpressure handling for overload scenarios
- Optimize resource allocation and recycling
中文:
用户需要在Linkis平台上同时提交大量Hive作业,要求系统能够稳定高效地处理。
期望改进:
- 增加每个Hive EC的最大并发作业限制
- 优化连接池大小和生命周期管理
- 改进作业队列和调度机制
- 为过载场景添加背压处理
- 优化资源分配和回收
How to reproduce
English:
- Configure Hive engine in Linkis
- Submit 50+ concurrent Hive SQL jobs
- Monitor job execution status and system performance
- Observe job queuing, delays, or timeout failures
中文:
- 在Linkis中配置Hive引擎
- 提交50+个并发Hive SQL作业
- 监控作业执行状态和系统性能
- 观察作业排队、延迟或超时失败
Anything else
English:
Suggested Solutions:
- Analyze Hive engine concurrency bottlenecks: Profile to identify performance hotspots
- Optimize connection pool management:
- Increase HiveServer2 connection pool size
- Implement connection reuse and lifecycle management
- Enhance concurrent job scheduling and execution mechanism:
- Implement job prioritization
- Add fair scheduling policies
- Optimize thread pool configuration
- Conduct high-concurrency scenario performance testing and optimization:
- Load testing with 100+ concurrent jobs
- Tune JVM parameters for high concurrency
- Optimize resource allocation and recycling mechanism:
- Implement dynamic resource allocation
- Add resource cleanup on job completion
Technical Considerations:
- HiveServer2 connection pooling (HikariCP recommended)
- Executor thread pool sizing (based on core count and workload)
- Memory management for concurrent queries
- Metastore connection pool optimization
- Query result caching strategy
中文:
建议解决方案:
- 分析Hive引擎并发处理的瓶颈:进行性能分析以识别性能热点
- 优化Hive引擎的连接池管理:
- 增加HiveServer2连接池大小
- 实现连接重用和生命周期管理
- 增强并发作业的调度和执行机制:
- 实现作业优先级
- 添加公平调度策略
- 优化线程池配置
- 进行高并发场景下的性能测试和优化:
- 使用100+并发作业进行负载测试
- 为高并发调优JVM参数
- 优化资源分配和回收机制:
- 实现动态资源分配
- 在作业完成时添加资源清理
技术考虑:
- HiveServer2连接池(推荐HikariCP)
- 执行器线程池大小(基于核心数和工作负载)
- 并发查询的内存管理
- Metastore连接池优化
- 查询结果缓存策略
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
- Dominant language
- Java
- Stars
- 3.4k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/linkis
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 86/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
[BUG]茶杯方块在取茶时会引发崩溃 Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
1.0.0-alpha2 Type/Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/dpdp-accelerator#272 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
area/frontend
Difficulty 2/5 1-3 hours Newbie friendliness 65/100