-
Notifications
You must be signed in to change notification settings - Fork 916
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TASK][MEDIUM] Engine adaptive pool size #5373
Comments
I am interested in this and I expect to achieve it in a month, can i take this? |
Hi , I also interested in this task, can you assign it to me ? I expect to achieve it in a month Thanks. |
@Kwafoor @lsm1 thanks for your passion, I suggest you discuss offline first :) |
If you're still interested in this, I can try other tasks. |
Yes, I want to achieve it, thanks a lot |
Code of Conduct
Search before creating
Mentor
Skill requirements
Background and Goals
In
kyuubi.engine.share.level
non-CONNECTION mode, how many engines the Kyuubi server starts is determined bykyuubi.engine.pool.size
.The engine selection policy is determined by
kyuubi.engine.pool.selectPolicy
. The default isRANDOM
, which means randomly selecting a number within the engine pool size range and checking whether the engine corresponding to this number has been created. If not, create one.When
kyuubi.engine.pool.size
is a relatively large value, it may randomly create many engines.In addition,
kyuubi.session.engine.idle.timeout
configures a relatively large idle time, so that once the engine is created, it will be slower to release the engine.This selection strategy is a bit of a waste of resources, especially since it takes a while to start the spark cluster mode.
Implementation steps
We can expose some information about the engine load in the Engine. When the server selects the engine, it will decide whether to use a new engine or reuse the old engine based on the load.
Additional context
Original reporter is @cxzl25
Introduction of #6232
The text was updated successfully, but these errors were encountered: