You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Experience error while sending data (in my case I got the following error):
influxdb2client E! Write error: unprocessable entity: failure writing points to database: partial write: field type conflict: input field "value" on measurement "xxxxxx" is type unsigned, already exists as type integer dropped=28
De init client by calling client.Close()
Expected behaviour: client.Close() will not block by unsuccessful flushing.
Actual behavior: client.Close() blocked by calling write API Flush():
Stack trace of blocked goroutine:
The text was updated successfully, but these errors were encountered:
i-prudnikov
changed the title
Client.Close() cause blocking during write API Flush() if (?) it can't send metrics
Client.Close() blocked by write API Flush() (if (?) it can't send metrics)
Mar 22, 2022
@i-prudnikov, I cannot reproduce this. There is no logic for waiting for unsuccessful writes. Flushing could be blocked if you have another routine which is still writing when you are closing the client.
Could you, please, enable debug logging, reproduce the issue, and past the log here?
Hi @vlastahajek,
I did double check and found out that the reason of blocking is channel returned by writeAPI.Errors()
So if writeAPI is asked for a channel even like this _ = writeAPI.Errors() then it leads to a deadlock if error occurred but the error channel is not pooled. So looks like a feature not a bug. Though I would vote for a non-blocking write into an error channel, otherwise seemed confusing.
Feel free to close the issue.
Steps to reproduce:
client.Close()
Expected behaviour:
client.Close()
will not block by unsuccessful flushing.Actual behavior:
client.Close()
blocked by calling write APIFlush()
:Stack trace of blocked goroutine:
Specifications:
The text was updated successfully, but these errors were encountered: