Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Chainsync termination doesn't trigger TX submission termination. #4954

Open
karknu opened this issue Sep 10, 2024 · 1 comment
Open

Chainsync termination doesn't trigger TX submission termination. #4954

karknu opened this issue Sep 10, 2024 · 1 comment
Labels
bug Something isn't working tx-submission Issues related to tx-submission protocol

Comments

@karknu
Copy link
Contributor

karknu commented Sep 10, 2024

A peer that responds with IntersectNotFound will cause the node to terminate the Chainsync protocol with Done. However this does not appear to cause the connection to be torn down. TX submission is still running towards the pear.
@karknu karknu self-assigned this Sep 10, 2024
@karknu
Copy link
Contributor Author

karknu commented Sep 10, 2024

There is a 300s timeout so if TX submission isn't able to terminate promptly the connection will get killed in 300s.

In the future the StTxIdsNonBlocking state should be updated to permit the transmission of MsgDone .

@karknu karknu removed their assignment Sep 10, 2024
@karknu karknu added bug Something isn't working tx-submission Issues related to tx-submission protocol labels Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working tx-submission Issues related to tx-submission protocol
Projects
Ouroboros Network
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@karknu