-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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.
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
[0.13.0] Can't start database with too many series #6903
Comments
@josselin-c I would imagine that this is being caused by too many series in the database. As the instance tries to load all the tag values into memory, it runs out causing the OOM kill. Do you have any estimate for how many series are in the dataset in question? I would also recomend looking at our technical paper on performance tuning |
This may help: #6952 |
@jackzampolin From what I recall, the OOM only triggered once. After it triggered, influxdb was unable to restart and keept crashing during data reload with the stacktrace above. During restart, OOM was not triggered. |
The PR I referenced "also fixes a panic that could occur to duplicate data stored within a block" I have no idea if it is that panic or not, but that all I was thinking... perhaps worth a try? |
Fixed via bc76048 |
Bug report
System info:
On debian Jessie - 32GB of ram dedicated to influxdb
InfluxDB starting, version 0.13.0, branch 0.13, commit e57fb88
Go version go1.6.2, GOMAXPROCS set to 8
Steps to reproduce:
Expected behavior:
Influxdb should restart correctly even when killed improperly
Actual behavior:
After an OOM Killer, influxdb isn't able to restart again and keeps crashing
Removing the folder containing the corrupted? database, influxdb restarts correctly
Additional info:
Here is the stacktrace:
The text was updated successfully, but these errors were encountered: