Orientdb Enterprise edition workbench issue with tcp + 2.0.10 and 2.1-rc3

42 views
Skip to first unread message

Darren Blaber

unread,
May 27, 2015, 5:58:30 PM5/27/15
to orient-...@googlegroups.com
Hello,
I have upgrade to orientdb 2.1-rc3 (and also tested 2.0.10), and the enterprise workbench (I am a developer evaluating enterprise edition) is unable to join my tcp only cluster.
I see this, and then eventually get an out of memory exception, it seems to try to join the cluster at different tcp ports many many times:
2015-05-27 17:17:33:622 WARNING [10.x.x.212]:2442 [UsageCluster] [3.3] This node does not have a connection to Member [10.x.x.212]:2443 [ClusterService][10.x.x.212]
:2443 [UsageCluster] [3.3] Call BasicInvocation{ serviceName='hz:core:clusterService', op=PostJoinOperation{operations=[com.hazelcast.spi.impl.EventServiceImpl$PostJoinRegistrationOperation@5828665f, com.hazelcast.map.operation.PostJoinMapOperation@21c5fc28]}, partitionId=-1, replicaIndex=0, tryCount=10, tryPauseMillis=100, invokeCount=2, callTimeout=60000, target=Address[10.x.x.212]:2436} encountered a timeout
java.util.concurrent.TimeoutException: Call BasicInvocation{ serviceName='hz:core:clusterService', op=PostJoinOperation{operations=[com.hazelcast.spi.impl.EventServiceImpl$PostJoinRegistrationOperation@5828665f, com.hazelcast.map.operation.PostJoinMapOperation@21c5fc28]}, partitionId=-1, replicaIndex=0, tryCount=10, tryPauseMillis=100, invokeCount=2, callTimeout=60000, target=Address[10.x.x.212]:2436} encountered a timeout
        at com.hazelcast.spi.impl.BasicInvocationFuture.resolveApplicationResponse(BasicInvocationFuture.java:321)
        at com.hazelcast.spi.impl.BasicInvocationFuture.resolveApplicationResponseOrThrowException(BasicInvocationFuture.java:289)
        at com.hazelcast.spi.impl.BasicInvocationFuture.get(BasicInvocationFuture.java:181)
        at com.hazelcast.util.FutureUtil.executeWithDeadline(FutureUtil.java:314)
        at com.hazelcast.util.FutureUtil.waitWithDeadline(FutureUtil.java:281)
        at com.hazelcast.util.FutureUtil.waitWithDeadline(FutureUtil.java:254)
        at com.hazelcast.cluster.FinalizeJoinOperation.run(FinalizeJoinOperation.java:87)
        at com.hazelcast.spi.impl.BasicOperationService$OperationHandler.handle(BasicOperationService.java:699)
        at com.hazelcast.spi.impl.BasicOperationService$OperationHandler.access$400(BasicOperationService.java:675)
        at com.hazelcast.spi.impl.BasicOperationService$OperationPacketHandler.handle(BasicOperationService.java:649)
        at com.hazelcast.spi.impl.BasicOperationService$OperationPacketHandler.handle(BasicOperationService.java:604)
        at com.hazelcast.spi.impl.BasicOperationService$OperationPacketHandler.access$1400(BasicOperationService.java:591)
        at com.hazelcast.spi.impl.BasicOperationService$BasicDispatcherImpl.dispatch(BasicOperationService.java:543)
        at com.hazelcast.spi.impl.BasicOperationScheduler$OperationThread.process(BasicOperationScheduler.java:439)
        at com.hazelcast.spi.impl.BasicOperationScheduler$OperationThread.processPriorityMessages(BasicOperationScheduler.java:452)
        at com.hazelcast.spi.impl.BasicOperationScheduler$OperationThread.doRun(BasicOperationScheduler.java:432)
        at com.hazelcast.spi.impl.BasicOperationScheduler$OperationThread.run(BasicOperationScheduler.java:408)
I am able to replicate this with a one node cluster started with dserver, with tcp enabled. I eventually see (on the orientdb node)

Members [9] {
        Member [10.x.x.128]:2434 this
        Member [10.x.x.212]:2437
        Member [10.x.x.212]:2438
        Member [10.x.x.212]:2439
        Member [10.x.x.212]:2440
        Member [10.x.x.212]:2441
        Member [10.x.x.212]:2442
        Member [10.x.x.212]:2443
        Member [10.x.x.212]:2444
When I only have a one node cluster (and just trying to join workbench). Did something change in latest hotfix/rc3 to prevent this from working? Thanks!
Reply all
Reply to author
Forward
0 new messages