Skip to content
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

fix: properly retrieve and close scalers cache #4012

Merged
merged 1 commit into from
Dec 15, 2022

Conversation

zroubalik
Copy link
Member

Signed-off-by: Zbynek Roubalik [email protected]

The latest refactoring done in #2282 introduced a regression in ScaledJobs. Scalers cache hasn't been used and a new scaler(and connection) has been opened for each request.

Fixes #4011

Relates to #2282

@zroubalik zroubalik requested a review from a team as a code owner December 14, 2022 13:49
@zroubalik
Copy link
Member Author

zroubalik commented Dec 14, 2022

/run-e2e
Update: You can check the progress here

@JorTurFer
Copy link
Member

JorTurFer commented Dec 14, 2022

/run-e2e
Update: You can check the progress here

@zroubalik zroubalik merged commit 06f6f7d into kedacore:main Dec 15, 2022
zroubalik added a commit to zroubalik/keda that referenced this pull request Jan 16, 2023
Signed-off-by: Zbynek Roubalik <[email protected]>

Signed-off-by: Zbynek Roubalik <[email protected]>
@JorTurFer JorTurFer mentioned this pull request Jan 17, 2023
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Connections leak in scalers defined in ScaledJob
2 participants