Skip to content

Conversation

@fracasula
Copy link
Collaborator

🔒 Scanned for secrets using gitleaks version is set by build process

Description

Attempt to fix keep alive issues during scaling operations:

2025/10/31 12:59:26 ERROR: [transport] Client received GoAway with error code ENHANCE_YOUR_CALM and debug data equal to ASCII "too_many_pings".
2025-10-31T12:59:27.237Z    WARN    scaler    scaler/scaler.go:344    Cannot create snapshots    {"nodeID": 0, "attempt": 2, "retryDelay": 1.013380069, "canonicalTarget": "dns:///keydb-0.keydb-headless.cloudwalk.svc.cluster.local:50051", "connState": "IDLE", "error": "rpc error: code = Unavailable desc = closing transport due to: connection error: desc = \"error reading from server: EOF\", received prior goaway: code: ENHANCE_YOUR_CALM, debug data: \"too_many_pings\""}

Linear Ticket

< Fixes PIPE-2511 >

Security

  • The code changed/added as part of this pull request won't create any security issues with how the software is being used.

🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
🔒 Scanned for secrets using gitleaks version is set by build process
@sonarqubecloud
Copy link

sonarqubecloud bot commented Nov 6, 2025

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.

1 participant