Details
-
Improvement
-
Resolution: Won't Fix
-
Major
-
2.2.0
-
Security Level: Public
-
None
-
our solution is deployed in environment, where tcp-connections are resources.
and are dropped on inactivity of 1 hour.
we can't change this.
Description
1. moxi initiates connection to couchbase to get cluster-map and it's updates.
2. since normally there are no updates, this connection gets silently dropped by a network element that treats connections as valuable resources.
3. new bucket/rebalance
4. couchbase cluster-map get changed
5. couchbase tries to push cluster-map updates down to moxi
6. tcp packet get silently dropped by network element in the middle
we can't change behavior of this network element.
we want moxi to regularly check that vital tcp connection with cluster-map updates is still alive, and, if not, reconnect automatically.