Skip to content

Reconnect passive dlt-daemon when passive dlt-daemon becomes unrespon… - #581

Closed
jianjun-huang wants to merge 1 commit into
COVESA:masterfrom
jianjun-huang:reconnect_passive_dlt_daemon
Closed

Reconnect passive dlt-daemon when passive dlt-daemon becomes unrespon…#581
jianjun-huang wants to merge 1 commit into
COVESA:masterfrom
jianjun-huang:reconnect_passive_dlt_daemon

Conversation

@jianjun-huang

Copy link
Copy Markdown

…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
Copy Markdown
Collaborator

Look greate, on review.
Thank you!

@minminlittleshrimp

Copy link
Copy Markdown
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
Copy Markdown
Collaborator

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

@minminlittleshrimp

Copy link
Copy Markdown
Collaborator

THis is good but we need a more generic, solved here #912

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