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

Default value for KafkaActivationLagThreshold throws error #339

Open
aavarghese opened this issue Nov 21, 2022 · 4 comments
Open

Default value for KafkaActivationLagThreshold throws error #339

aavarghese opened this issue Nov 21, 2022 · 4 comments
Labels
triage/accepted Issues which should be fixed (post-triage)

Comments

@aavarghese
Copy link
Contributor

Issue: When using current default value in this repo for KedaAutoscalingKafkaActivationLagThreshold, it throws an error:

error parsing kafka metadata: "activationLagThreshold" must be positive number

Reason: KEDA has a validation check for ActivationLagThreshold
https://github.com/kedacore/keda/blob/03b35d2fbac00c6d921b218519da865861db6456/pkg/scalers/kafka_scaler.go#L232-L243 that fails when value is 0.

Solution: Default for ActivationLagThreshold must be changed to a positive number or validation logic modified. What is the allowed range for this scaling annotation?

cc: @zroubalik @pierDipi

@pierDipi
Copy link
Member

I think it makes sense to be a positive number only because it is specifying how many records there should be to scale from 0 to 1, since this is a default value, I think 1 is a good default so that we start consuming as soon as there is at least one record

@aavarghese
Copy link
Contributor Author

Agreed! @pierDipi

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 20, 2023
@pierDipi
Copy link
Member

/remove-lifecycle stale
/triage accepted

@knative-prow knative-prow bot added triage/accepted Issues which should be fixed (post-triage) and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants