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: Trino scale-down to zero with KEDA #726

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

bbgu1
Copy link
Contributor

@bbgu1 bbgu1 commented Jan 15, 2025

What does this PR do?

🛑 Please open an issue first to discuss any significant work and flesh out details/direction. When we triage the issues, we will add labels to the issue like "Enhancement", "Bug" which should indicate to you that this issue can be worked on and we are looking forward to your PR. We would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Changed KEDA scaled object to improve handling of scaling to zero. Adjusted doc accordingly.

Motivation

The current KEDA scaled object for Trino interrupts active query to scale down. The Trino coordinator often gets evicted when Karpenter replacing node with smaller instance as result of scaling down.

More

  • Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
  • Mandatory for new blueprints. Yes, I have added a example to support my blueprint PR
  • Mandatory for new blueprints. Yes, I have updated the website/docs or website/blog section for this feature
  • Yes, I ran pre-commit run -a with this PR. Link for installing pre-commit locally

For Moderators

  • E2E Test successfully complete before merge?

Additional Notes

@bbgu1 bbgu1 changed the title Trino keda fix: Trino scale-down to zero with KEDA Jan 15, 2025
Copy link
Collaborator

@ratnopamc ratnopamc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @bbgu1 👍🏼 . Left a few comments to address.

Comment on lines -28 to -29
repository_username = data.aws_ecrpublic_authorization_token.token.user_name
repository_password = data.aws_ecrpublic_authorization_token.token.password
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any specific reason for omitting this? This would result in 403 while accessing karpenter helm_chart.

```

Now, lets access the Trino UI by pasting above Load Balancer DNS in a web browser and login with username `admin` in the login window as shown below:
Now, lets access the Trino UI at `http://localhost:8080` through web browser and login with username `admin` in the login window as shown below:

![Trino UI Login](./img/trino-ui-login.PNG)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please replace the Trino UI screenshot with "0" Active Workers to match the initial 0 active worker configuration above.


![Trino UI Login](./img/trino-ui-login.PNG)

We can see Trino Web UI showing 3 active workers
Example of Trino Web UI showing 3 active workers:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"0" workers

name = "karpenter"
repository = "oci://public.ecr.aws/karpenter"
chart = "karpenter"
version = "1.0.6"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we also update to the latest Karpenter version 1.1.1?

@ratnopamc ratnopamc requested a review from vara-bonthu January 16, 2025 07:41
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.

2 participants