In one of customers (on EC2) we had some strange case as noted in SUBJ. Quite possibly there was some serious lack of CPU for VM, but let's at least inspect code for other possible causes of this problem.
While it's possible to have some nodes down and rebalance continuing with current code, I've found no way how complete disconnect of master node can not fail rebalance. Closing. And I think this customer's case is something about environment, possibly EC2 just took CPU away from them for some reason
Aleksey Kondratenko
added a comment - While it's possible to have some nodes down and rebalance continuing with current code, I've found no way how complete disconnect of master node can not fail rebalance. Closing. And I think this customer's case is something about environment, possibly EC2 just took CPU away from them for some reason
set keepalive on ebucketmigrator sockets.
MB-5049(Revision 57455f88120465bc89ee4cad14c09abe97fe8688)Result = SUCCESS
Aliaksey Kandratsenka :
Files :
* src/ebucketmigrator_srv.erl