Skip to content

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

Open
dburton-influxdata wants to merge 1 commit into
influxdata:masterfrom
dburton-influxdata:fix/influxdb3-enterprise-probe-timeouts
Open

Fix: Increase startup probe timeout for influxdb3-enterprise 3.2+#801
dburton-influxdata wants to merge 1 commit into
influxdata:masterfrom
dburton-influxdata:fix/influxdb3-enterprise-probe-timeouts

Conversation

@dburton-influxdata

Copy link
Copy Markdown

Description

This PR fixes CrashLoopBackOff issues in InfluxDB 3.2+ deployments by increasing the startup probe timeout to accommodate longer initialization times.

Fixes #800

Changes

Chart Version

  • Bump version from \

- Increase startup probe initialDelaySeconds from 10s to 30s
- Increase startup probe periodSeconds from 5s to 10s
- Increase startup probe timeoutSeconds from 5s to 10s
- Increase startup probe failureThreshold from 12 to 20
- Total startup window increased from 70s to 230s

This change addresses startup failures in InfluxDB 3.2+ where initialization
time increased to ~100 seconds due to:
- Python Processing Engine initialization
- WAL recovery operations
- V2 compaction consumer preloading

The new configuration provides a 2.3x safety buffer for typical 100s startups,
compared to the previous 4-5x buffer for 15s startups.

Fixes pod CrashLoopBackOff with exit code 137 (SIGKILL) on 3.2 deployments.

Bump chart version to 0.1.1
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.

influxdb3-enterprise: Startup probe timeout too short for v3.2+

1 participant