Skip to content

Fix: Increase startup probe timeout for influxdb3-enterprise 3.2+ #801

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

Closed
dburton-influxdata wants to merge 1 commit into from
Closed

Fix: Increase startup probe timeout for influxdb3-enterprise 3.2+ #801

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion charts/influxdb3-enterprise/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ apiVersion: v2
name: influxdb3-enterprise
description: A Helm chart for deploying InfluxDB 3 Enterprise on Kubernetes
type: application
version: 0.1.0
version: 0.1.1
appVersion: "3.6.0"
keywords:
- influxdb
Expand Down
11 changes: 6 additions & 5 deletions charts/influxdb3-enterprise/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -614,12 +614,13 @@ probes:

# Startup probe settings
# Protects container during initialization. Once successful, never runs again.
# For ~15s startup: 10s initial + (12 × 5s) = 70s total (4-5x safety buffer)
# For ~100s startup in 3.2: 30s initial + (20 × 10s) = 230s total (~2.3x safety buffer)
# Accounts for Python Processing Engine initialization, WAL recovery, and compaction preloading
startup:
initialDelaySeconds: 10 # Wait ~50% of expected startup time
periodSeconds: 5 # Check every 5 seconds
timeoutSeconds: 5
failureThreshold: 12 # 10s + (12 × 5s) = 70s total
initialDelaySeconds: 30 # Wait ~30% of expected startup time
periodSeconds: 10 # Check every 10 seconds (less aggressive)
timeoutSeconds: 10 # Increased timeout for slower environments
failureThreshold: 20 # 30s + (20 × 10s) = 230s total

# Liveness probe settings
# Only starts checking AFTER startup probe succeeds
Expand Down