influxdata / influxdata/influxdb

InfluxDB doesn't start after delete org with tasks

Open
#24,067 5 comments 1 reaction 0 assignees View on GitHub
area/tasks kind/bug
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.

1. create org
2. create sheduled tasks in the org
3. delete org
4. create the same empty org
5. restart server

__Actual behavior:__
Doesn't start, even with --no-tasks

__Environment info:__

* System info: Linux 4.19.0-23-amd64 x86_64
* InfluxDB version: InfluxDB v2.6.1 (git: 9dcf880fe0) build_date: 2022-12-29T15:53:07Z

__Logs:__
```
Jan 26 23:42:57 influxdb influxd-systemd-start.sh[625]: ts=2023-01-26T22:42:57.236728Z lvl=error msg="err finding runs:" log_id=0fd3ly9W000 service=task-executor error="bucket \"_tasks\" not found"
Jan 26 23:42:57 influxdb influxd-systemd-start.sh[625]: ts=2023-01-26T22:42:57.236767Z lvl=fatal msg="could not load existing scheduled runs" log_id=0fd3ly9W000 error="bucket \"_tasks\" not found"
.....

Jan 26 23:35:46 influxdb influxd-systemd-start.sh[608]: InfluxDB API at http://localhost:8086/ready unavailable after 58 attempts...
Jan 26 23:35:47 influxdb influxd-systemd-start.sh[608]: InfluxDB API at http://localhost:8086/ready unavailable after 59 attempts...
Jan 26 23:35:48 influxdb influxd-systemd-start.sh[608]: InfluxDB API at http://localhost:8086/ready unavailable after 60 attempts...
Jan 26 23:35:49 influxdb influxd-systemd-start.sh[608]: InfluxDB API at http://localhost:8086/ready unavailable after 61 attempts...
Jan 26 23:35:50 influxdb influxd-systemd-start.sh[608]: InfluxDB API at http://localhost:8086/ready unavailable after 62 attempts...
```

Contributor guide

Open the contributing guide

Research direction

Reproduce the sequence in the issue and inspect the startup logs, especially the task-executor error about the missing _tasks bucket and the repeated /ready failures. Determine why recreating the organization does not restore the scheduled-task state, then verify that the server starts successfully after the same sequence, including with --no-tasks.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.