-
Notifications
You must be signed in to change notification settings - Fork 18
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
Configure auto-healing mechanism for the rethinkdb connection #726
Comments
related tickets are zebrunner/mcloud-ios#54 and zebrunner/mcloud-ios#78 |
let's try to integrate recover kickstart approach when connection to rethinkdb is broken: zebrunner/mcloud-ios#151 under the question any kind of limits in recovery attempts... |
@dhreben, please retest. I hope our existing wda/stf healthcheck could solve it... Feel free to reopen if not so we review in details exact place where stf is srashed and where recovery kickstart should be added |
Still repro Logs iOS device:
|
moved to 2.4.6 as default recovery didn't resolve the problem |
@ignacionar, please take a look onto this one as well.
We have to improve stf doing explicit exit on this failure. it should activate recovery as for linux so for mac. |
Done: #727, when disconnecting from the db it should try to connect every 5 seconds. |
Reopened, still repro log:
|
@dhreben - please tests with rethinkdb restart. there is a limitation in retries so long pause will crash as expected... |
Verified. |
The following feature\functionality could be potentially useful when we have some network issues, for instance when network is down, rethinkdb becomes unavailable and it could be restored back only via manual interactions with required services (e.g. STF).
The text was updated successfully, but these errors were encountered: