Skip to content

Conversation

@jianjun-huang
Copy link

…sive

using DLT_SERVICE_ID_GET_DEFAULT_LOG_LEVEL message to detect whether dlt-daemon is active, then try to reconnect the passive dlt-daemon if the passive dlt-daemon is unresponsive

…sive

using DLT_SERVICE_ID_GET_DEFAULT_LOG_LEVEL message to detect whether dlt-daemon is active, then try to reconnect the passive dlt-daemon if the passive dlt-daemon is unresponsive
@minminlittleshrimp
Copy link
Collaborator

Look greate, on review.
Thank you!

@minminlittleshrimp
Copy link
Collaborator

Hello @Bichdao021195
Please kindly compare this solution with the one using setsockopt() with TCP keepalive.
I would prefer using the internal method/implementation rather than depending on tcp lib if it is possible.

@minminlittleshrimp
Copy link
Collaborator

Hello @michael-methner
Kindly review this patch.
Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DLT-Multinode: Gateway does not recognize reset of passive node

2 participants