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

Revert "NATS reconnect fully recreates TCP session" #1821

Merged
merged 3 commits into from Mar 3, 2020
Merged

Conversation

vkuznecovas
Copy link
Contributor

This reverts commit c7fbce9.

@vkuznecovas
Copy link
Contributor Author

Closes #1820

@zolia
Copy link
Contributor

zolia commented Mar 2, 2020

Looks, like this nats (disconnect fix) really brokes current broker messaging. @Waldz should we revert and wait for p2p communication implementation for direct messaging?

@anjmao
Copy link
Contributor

anjmao commented Mar 2, 2020

Reopen should:

  1. Recreate all active subscribes as they are still using old conn.
  2. Republish all messages which was in progress during Reopen but didn't success. If not whose messages will be lost.

@Waldz Waldz self-assigned this Mar 3, 2020
@Waldz Waldz merged commit 29d8167 into release/0.22 Mar 3, 2020
@Waldz Waldz deleted the fix-nats branch March 3, 2020 14:30
@@ -74,3 +74,5 @@ require (
gopkg.in/urfave/cli.v1 v1.20.0 // indirect
gopkg.in/yaml.v2 v2.2.8 // indirect
)

replace github.com/nats-io/go-nats v1.4.0 => github.com/mysteriumnetwork/nats.go v1.4.1-0.20200303115848-b4a5324c56ed
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it really required to have a custom version of nats?

@soffokl
Copy link
Member

soffokl commented Mar 3, 2020

This PR was approved as a revert of the commit. But now it merged with completely different changes without review. :/

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

Successfully merging this pull request may close these issues.

None yet

5 participants