We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, We have observed the following issue - when using the batch processor, when the connection to db fails, then exception is thrown during https://github.com/influxdata/influxdb-java/blob/master/src/main/java/org/influxdb/impl/BatchProcessor.java#L166 . According to https://github.com/influxdata/influxdb-java/blob/master/src/main/java/org/influxdb/impl/BatchProcessor.java#L137 scheduleAtFixedRate java doc If any execution of the task * encounters an exception, subsequent executions are suppressed. So after connection exception next execution is surpresed and batch will be only send when the max size is reached during put.
scheduleAtFixedRate
If any execution of the task * encounters an exception, subsequent executions are suppressed.
put
The text was updated successfully, but these errors were encountered:
Same as issue #118
Sorry, something went wrong.
No branches or pull requests
Hi,
We have observed the following issue - when using the batch processor, when the connection to db fails, then exception is thrown during https://github.com/influxdata/influxdb-java/blob/master/src/main/java/org/influxdb/impl/BatchProcessor.java#L166 . According to https://github.com/influxdata/influxdb-java/blob/master/src/main/java/org/influxdb/impl/BatchProcessor.java#L137
scheduleAtFixedRate
java docIf any execution of the task * encounters an exception, subsequent executions are suppressed.
So after connection exception next execution is surpresed and batch will be only send when the max size is reached during
put
.The text was updated successfully, but these errors were encountered: