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.

Sign up for GitHub

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

Jump to bottom

external server create too may gRPC connection #3193

Closed
champly opened this issue Jun 20, 2022 · 0 comments · Fixed by #3184
Closed

external server create too may gRPC connection #3193

champly opened this issue Jun 20, 2022 · 0 comments · Fixed by #3184
Assignees
@champly
Labels
bug Something isn't working

Comments

@champly
Copy link
Contributor

champly commented Jun 20, 2022

Report

When we use external and external-push extensions, kdea will create a gRPC connection for each request, and use metadata as hashkey will result in a gRPC connection per ScalerObject

Expected Behavior

The same address use the same connection.

Actual Behavior

Create too many gRPC connection

Steps to Reproduce the Problem

create external server will got

transport: http2Server.HandleStreams failed to read frame: read tcp 10.49.19.213:8080->10.248.227.73:53532

Logs from KEDA operator

example

KEDA Version

No response

Kubernetes Version

No response

Platform

No response

Scaler Details

No response

Anything else?

No response
@champly champly added the bug Something isn't working label Jun 20, 2022
@champly champly mentioned this issue Jun 20, 2022
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@champly champly

Labels
bug Something isn't working
Projects
Roadmap - KEDA Core
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

reduce gRPC connection create
1 participant
@champly