RethinkDbPublisher, define timeout
See original GitHub issueWhen there are problems of connectivity with RethinkDbPublisher
executions hangs with:
[RethinkDbPublisher]: ================
[RethinkDbPublisher]: RethinkDbPublisher
[RethinkDbPublisher]: publishBuildMetrics: true
[RethinkDbPublisher]: publishTaskMetrics: true
[RethinkDbPublisher]: ================
[Talaiot]: Shutting down executor. Not yet. Still waiting for termination
[Talaiot]: Shutting down executor. Not yet. Still waiting for termination
[Talaiot]: Shutting down executor. Not yet. Still waiting for termination
[Talaiot]: Shutting down executor. Not yet. Still waiting for termination
[Talaiot]: Shutting down executor. Not yet. Still waiting for termination
[Talaiot]: Shutting down executor. Not yet. Still waiting for termination
Check timeout options in RethinkDbPublisher
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
ReQL command: wait - RethinkDB
timeout : a number indicating maximum time, in seconds, to wait for the table to be ready. If this value is exceeded, a...
Read more >ReQL command: next - RethinkDB
Calling next the first time on a cursor provides the first element of the cursor. If the data set is exhausted (e.g., you...
Read more >ReQL command: js - RethinkDB
timeout is the number of seconds before r.js times out. The default value is 5 seconds. Whenever possible, you should use native ReQL...
Read more >RethinkDB command line options
Many of these options can also be set in the configuration file; read Configuration ... --cluster-reconnect-timeout secs : the amount of time, in...
Read more >Fix timeout errors in Zaps - Zapier
A timeout error, or a message that your request has timed out, means that the app Zapier is trying to connect to is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sorry I’m afraid I don’t have enough knowledge to give a valuable input here. I’ll definitely take a closer look at the implementation to learn more. btw, time to time I also see
with
InfluxDbPublisher
, but only one occurrence per build.Hi @mokkun First, yep, the case using
awaitTermination
covers the case for theRethinkDbPublisher
. It should be applied for the other publishers, but in case of InfluxDb it’s defined in the api of the influx client.This bring to your second point about the “Network” implementation for the interface Publisher. I’m absolutely agree. Talaiot needs to implement a consistent network layer. Before entering in details I have some notes:
RethinkDbPublisher
-->com.rethinkdb:rethinkdb-driver:
–ElasticDbPublisher
-->org.elasticsearch.client:elasticsearch-rest-high-level-client:7.3.0
–InfluxDb
-->org.influxdb:influxdb-java:
Do you have more notes? @MyDogTom do you have any suggestions/notes for this rework of the Network Layer? Once we have the notes/suggestion collected we can create the issues/tasks and start working in this rework.
So, thank you very much for this proposals, I really appreciate it.