-
Notifications
You must be signed in to change notification settings - Fork 129
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
WriteApi
does nothing after WriteRetriableErrorEvent
#357
Comments
Hi @olenagerasimova, thanks for using our client.
The default retry strategy for the next attempt is random distributed with following delays:
How looks like your event handler for Regards |
@bednar hi, thanks for the reply. About retry strategy: db is not available for about a minute in our case. Thus, retry events should definitely happen.
It just logs the error
We are still investigating, I'll add more details as soon as we understand them. |
I agree, there is no reason why the retry attempt should not be repeated.
Thanks for help with this. |
This is probably caused by same issue as is mentioned in #202 (comment). For more info see: #202 (comment) |
@bednar thanks, we tried snapshot version, it helped. |
Hi @olenagerasimova, The PR#358 is ready to review before merge into master. The development version is deployed into Any feedback and testing will be appreciate👂 Regards |
Hi, I'm using
influxdb-client-java
6.0.0 asynchronous non-blocking API to write data to Influx DB withwritePoint
method. If db is not available for some time,WriteRetriableErrorEvent
happens as expected with exception:After this event, nothing happens, no other attempts to write data.
WriteOptions
are not manually configured, I expect default values to work.Steps to reproduce:
WriteRetriableErrorEvent
to appearExpected behavior:
Influx client tries to connect to db and white data again. If db is avaliable again in 3 seconds or less, data should be written successfully.
Actual behavior:
Influx client does nothing.
Specifications:
The text was updated successfully, but these errors were encountered: