We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If the offset lag cannot be polled return 0 and do not crash with SIGSEGV.
keda-operator crashs with SIGSEGV:
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x13c43ad] goroutine 1544 [running]: github.com/kedacore/keda/pkg/scalers.(*kafkaScaler).getLagForPartition(0xc0008f03c0, 0xc000000017, 0xc000978de0, 0x32) keda/pkg/scalers/kafka_scaler.go:281 +0x5d github.com/kedacore/keda/pkg/scalers.(*kafkaScaler).IsActive(0xc0008f03c0, 0x21c2060, 0xc0017d0200, 0x1, 0x1, 0xc0016d2900) keda/pkg/scalers/kafka_scaler.go:168 +0xe0 github.com/kedacore/keda/pkg/handler.(*ScaleHandler).handleScaleDeployment(0xc0008aa630, 0x21c2060, 0xc0017d0200, 0xc000b96340) keda/pkg/handler/scale_loop.go:119 +0x11a github.com/kedacore/keda/pkg/handler.(*ScaleHandler).handleScale(0xc0008aa630, 0x21c2060, 0xc0017d0200, 0xc000b96340) keda/pkg/handler/scale_loop.go:45 +0x6b github.com/kedacore/keda/pkg/handler.(*ScaleHandler).HandleScaleLoop(0xc0008aa630, 0x21c2060, 0xc0017d0200, 0xc000b96340) keda/pkg/handler/scale_loop.go:14 +0x1d2 created by github.com/kedacore/keda/pkg/controller/scaledobject.(*ReconcileScaledObject).startScaleLoop keda/pkg/controller/scaledobject/scaledobject_controller.go:333 +0x35f
This problem occurs only when a kafka topic partition is not clean and ready to use. I have seen that when a broker as partition leader restarts.
The text was updated successfully, but these errors were encountered:
Add Stilingue as KEDA user (kedacore#688)
1368885
Successfully merging a pull request may close this issue.
Expected Behavior
If the offset lag cannot be polled return 0 and do not crash with SIGSEGV.
Actual Behavior
keda-operator crashs with SIGSEGV:
Steps to Reproduce the Problem
This problem occurs only when a kafka topic partition is not clean and ready to use. I have seen that when a broker as partition leader restarts.
Specifications
The text was updated successfully, but these errors were encountered: