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

[M2] DMSG transports fail to deliver packets after visor restart #171

Closed
Darkren opened this issue Feb 28, 2020 · 0 comments · Fixed by #166
Closed

[M2] DMSG transports fail to deliver packets after visor restart #171

Darkren opened this issue Feb 28, 2020 · 0 comments · Fixed by #166
Assignees
Labels
bug Something isn't working

Comments

@Darkren
Copy link
Contributor

Darkren commented Feb 28, 2020

Describe the bug
Currently working on this PR #152 . The router part there is stable, everything is working great with STCP, but the same tests fail for DMSG transports. We may see the following in logs of visor C.

First, there is this line:

time="2020-02-25T08:38:34+03:00" level=warning msg="route finder: no route to destination" source="retrier.go:90"

Happens a couple of times. After 5-10 seconds these appear:

failed to redial underlying connection (redial loop): settlement handshake failed: context deadline exceeded
Failed to update statuses error="Post http://localhost:9091/statuses: context deadline exceeded"

Then transport show UP status but starts spamming the following:

WARN [tp:0348c9]: failed to read packet: EOF

And packets are not being delivered

Environment information:
Independent

Steps to Reproduce
Steps to reproduce the behavior:

  • run the proxy integration env
  • perform startup
  • send single curl (may be found in test-proxy.sh)
  • kill -9 visor C
  • wait for route to time out (currently like 2 minutes, this may be observed in logs of visor A, route group will get closed)
  • run visor C and try to do curl again
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants