-
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.9.2] Panic immediately after restarting due to write timeouts #3468
Comments
@jhorwit2 what did your write payloads look like? how many points per batch, cardinality, etc? how long were you writing data before you saw the timeouts? |
Payloads very, but I have been sending the data for over a week now on 0.9.1 without issues. I upgraded this morning around 9am and response times peaked around 1:30. I have 4 servers sending anywhere between 200-500 points in each write and they each average about 1 write per second, so 800-2k points per second getting sent to influx. Tags are sorted. Points are sorted in asc by timestamp. The fields have a lot of cardinality, but the tags have very low cardinality (under 100). Example payload of one endpoint
As far as fields go, every request for each measurement has the same fields with some value (whether blank or not) |
I keep getting this and it appears to be tied to a CQ query timeout, which causes cascading timeouts across the application (#3469). I have noticed since the upgrade to 0.9.2, the restart hasn't been as graceful. I always get this no matter if I stop/start or restart with or without errors.
The server will start fine though. |
Should be solved with 0.9.3. Please reopen if that isn't the case. |
I noticed my writes started to timeout at 5 seconds, so I attempted to restart influx to allow it to catch up; however, upon restart it immediately paniced.
The text was updated successfully, but these errors were encountered: