-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Blocked until restarted 'influxd.exe' #13425
Comments
I also encountered the same problem, after some sensitive operations, some databases will fall into an unavailable state. I have encountered this problem twice. The first time I use the influx_inspect tool to export the data of a certain database in the influxdb running state, then the database will be inserted into the query or the query will be in a deadlock state, while other databases have no effect. The second time is the write test, try to change the value type, after the command is executed, the error message is time out, after which the database is in an unavailable state. |
However, the above situation did not always occur, and it was unsuccessful when many attempts were made to reproduce. I guess it is related to the synchronization modification when tsm or tsi files are merged. |
edit: probably same as #13010 I believe I am hitting the same issue as well. I setup a new influx server on 1.7.5 and setup a single telegraf agent to add some metrics. Some time later it stopped responding to any query. Looking at the influx http access logs i see the exact point it started failing. x.x.x.x - - [16/Apr/2019:14:21:00 -0500] "POST /write?consistency=any&db=network&rp=HighResolution HTTP/1.1" 204 0 "-" "Telegraf/1.10.2" c4796750-607c-11e9-89c7-00505681237f 4721 Restarting influx would fix the problem for a bit, but it kept coming back. Curious to see if it was telegraf i downgraded the the telegraf version without restarting influx. This did nothing, so pretty sure its not related to what telegraf was sending. I did packet capture of the requests coming from telegraf and they looked completely normal. x.x.x.x - - [16/Apr/2019:15:15:40 -0500] "POST /write?consistency=any&db=network&rp=HighResolution HTTP/1.1" 500 20 "-" "Telegraf/1.10.2" 6781bc77-6084-11e9-80e6-00505681237f 10009953 Non access logs show just repeat timeouts. I downgraded influxdb to 1.7.2(deployed elsewhere here with the same configuration) and havent seen a repeat of the issue. |
1.7.6 should be available now. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
OS: windows 7 x64
InfluxDB version : 1.7.5-1
Console 1:
D:\influxdb\influxdb-1.7.5-1>influx -username root -password 123456
Connected to http://localhost:8086 version 1.7.5
InfluxDB shell version: 1.7.5
Enter an InfluxQL query
Console 2:
D:\influxdb\influxdb-1.7.5-1>influx -username root -password 123456
Connected to http://localhost:8086 version 1.7.5
InfluxDB shell version: 1.7.5
Enter an InfluxQL query
When restarted 'influxd.exe'
Console 1:
Console 2:
DR_E_RAW_HOUR_20190415_1
load
The text was updated successfully, but these errors were encountered: