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

Unexpected Failover brokering #1249

Closed
YuanYuYuan opened this issue Jul 22, 2024 · 0 comments · Fixed by #1272
Closed

Unexpected Failover brokering #1249

YuanYuYuan opened this issue Jul 22, 2024 · 0 comments · Fixed by #1272
Labels
bug Something isn't working

Comments

@YuanYuYuan
Copy link
Contributor

YuanYuYuan commented Jul 22, 2024 •
edited
Loading

Describe the bug

Failover brokering is activated unexpectedly in the following order

  1. ./target/debug/zenohd -l tcp/127.0.0.1:7447
  2. ./target/debug/examples/z_sub -e tcp/127.0.0.1:7447 -m peer
  3. ./target/debug/examples/z_pub -e tcp/127.0.0.1:7447 -m peer

Note the below order doesn’t trigger.

  1. ./target/debug/zenohd -l tcp/127.0.0.1:7447
  2. ./target/debug/examples/z_pub -e tcp/127.0.0.1:7447 -m peer
  3. ./target/debug/examples/z_sub -e tcp/127.0.0.1:7447 -m peer

System info
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
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix failover brokering bug reacting to linkstate changes eclipse-zenoh/zenoh
2 participants
@OlivierHecart @YuanYuYuan