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.

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

bug: message not delivered during interop test #1014

Closed
romanzac opened this issue Jan 25, 2024 · 2 comments
Closed

bug: message not delivered during interop test #1014

romanzac opened this issue Jan 25, 2024 · 2 comments

Comments

@romanzac
Copy link
Collaborator

romanzac commented Jan 25, 2024

Problem

At rare occasion, message is not delivered when a node is shut down during the test sequence.

Impact

It is low occurrence, medium impact. The node may shut down before the message in sent to other nodes.

To reproduce

Run interop tests at https://github.com/waku-org/waku-interop-tests/actions/workflows/go_waku_daily.yml. Simillar issue happened also with nwaku during execution of test_publish_after_node1_restarts.

Expected behavior

Node which is shutting down should reject accepting new messages. When the message gets stuck, next time the node starts it retries the delivery. I would assume shutdown was part of a restart. Open question is what to do when node stays shut for long periods of time. Messages lost ?

Related to waku-org/nwaku#2369

Screenshots/logs

image

data_attachments_8d428324ec7625a3.txt

@chaitanyaprem
Copy link
Collaborator

Node which is shutting down should reject accepting new messages, When the message gets stuck, next time the node starts it retries the delivery. I would assume shutdown was part of a restart. Open question is what to do when node stays shut for long periods of time. Messages lost ?

I don't think it is a good idea to implement such synchronization mechanism as it will complicate and create lot more other issues.
It should be the responsibility of caller/user to ensure such scenarios are addressed.

Some of these scenarios will have to be handled at application level, you can refer to discussion here for reference.

Closing this as this is not considered under go-waku scope.

@romanzac
Copy link
Collaborator Author

romanzac commented Mar 4, 2024

Another reliability problem happened during different test (not invoking node restart):
test_all_nodes_subscribed_to_the_topic

data_attachments_64e9303acd8f5de5.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants