Influxdb timeout after 90 seconds with systemd
Bug #1947882 reported by
Benjamin Allot
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| InfluxDB Charm |
Fix Committed
|
Low
|
Benjamin Allot | ||
Bug Description
Hello,
The influxdb package doesn't provide a TimeoutStartSec option, using the default 90 seconds one.
On a database worth 92 GB of data, it's not sufficient.
Adding "infinity" will let the administrator determine if a start should be stopped or not.
The same database took 312 seconds to start. I feel like putting a random number is never going to cut it anyway and monitoring will make sure the service is up anyway.
Related branches
~ballot/influxdb-charm/+git/influxdb-charm:lp1947882
- Tom Haddon: Approve
- Canonical IS Reviewers: Pending requested
-
Diff: 67 lines (+19/-0)3 files modifiedfiles/influxdb_override.conf (+2/-0)
layer.yaml (+1/-0)
reactive/influxdb.py (+16/-0)
| description: | updated |
| Changed in influxdb-charm: | |
| status: | New → Fix Committed |
| importance: | Undecided → Low |
| assignee: | nobody → Benjamin Allot (ballot) |
To post a comment you must log in.
