Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
1.7.2, 1.8.0
-
Security Level: Public
Description
screenshot attached
NOTE: we're converting this to main 'named tap issues' ticket.
So what's not safe about reusing named taps as of 1.8.0?
If something happened to destination node after tap was disconnected. And if that something affected data for vbuckets replicated as part of named tap, then subsequent reuse of named tap will incorrectly assume that we can continue sending stuff instead of re-negotiating which data needs to be resent.