[ https://issues.apache.org/jira/browse/ASTERIXDB-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326392#comment-16326392 ]
ASF subversion and git services commented on ASTERIXDB-2236: ------------------------------------------------------------ Commit d15f88881ea179eb5486d01ac8b502543b87b90e in asterixdb's branch refs/heads/master from [~mhubail] [ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=d15f888 ] [ASTERIXDB-2236][NET] Reestablish Nc2Nc Closed Connection - user model changes: no - storage format changes: no - interface changes: no Details: - Enable keep alive on Nc2Nc sockets. - Open Nc2Nc connection when closed. - Add "port" command to test framework to ensure a port is not used anymore. - Add test case for reestablishing connection between nodes. Change-Id: I3af4af37de6c1b36d7032c78ee60f1e5ca5f7c1c Reviewed-on: https://asterix-gerrit.ics.uci.edu/2273 Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Contrib: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Reviewed-by: Michael Blow <mb...@apache.org> > Nc2Nc Connection isn't Re-established After Failure > --------------------------------------------------- > > Key: ASTERIXDB-2236 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-2236 > Project: Apache AsterixDB > Issue Type: Bug > Components: NET - Network > Reporter: Murtadha Hubail > Assignee: Murtadha Hubail > Priority: Major > > When a node A loses connection with node B due to node B failure, when A > tries to connect to B, the connection will always fail even if B is back > again. > Stacktrace: > {code:java} > org.apache.hyracks.api.exceptions.HyracksDataException: > org.apache.hyracks.api.exceptions.NetException: Connection failure > at > org.apache.hyracks.comm.channels.NetworkInputChannel.open(NetworkInputChannel.java:98) > ~[hyracks-comm-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > at > org.apache.hyracks.dataflow.std.collectors.PartitionCollector.addPartitions(PartitionCollector.java:58) > ~[hyracks-dataflow-std-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > at org.apache.hyracks.control.nc.Task.pushFrames(Task.java:385) > ~[hyracks-control-nc-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > at org.apache.hyracks.control.nc.Task.run(Task.java:323) > [hyracks-control-nc-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [?:1.8.0_131] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [?:1.8.0_131] > at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131] > Caused by: org.apache.hyracks.api.exceptions.NetException: Connection failure > at > org.apache.hyracks.net.protocols.muxdemux.MultiplexedConnection.waitUntilConnected(MultiplexedConnection.java:124) > ~[hyracks-net-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > at > org.apache.hyracks.net.protocols.muxdemux.MuxDemux.connect(MuxDemux.java:145) > ~[hyracks-net-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > at > org.apache.hyracks.control.nc.net.NetworkManager.connect(NetworkManager.java:104) > ~[hyracks-control-nc-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > at > org.apache.hyracks.control.nc.net.NetworkManager.connect(NetworkManager.java:45) > ~[hyracks-control-nc-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > at > org.apache.hyracks.comm.channels.NetworkInputChannel.open(NetworkInputChannel.java:96) > ~[hyracks-comm-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > ... 6 more > Caused by: org.apache.hyracks.api.exceptions.NetException: Socket Closed > at > org.apache.hyracks.net.protocols.muxdemux.MultiplexedConnection.driveReaderStateMachine(MultiplexedConnection.java:361) > ~[hyracks-net-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > at > org.apache.hyracks.net.protocols.muxdemux.MultiplexedConnection.notifyIOReady(MultiplexedConnection.java:132) > ~[hyracks-net-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > at > org.apache.hyracks.net.protocols.tcp.TCPEndpoint$IOThread.run(TCPEndpoint.java:175) > ~[hyracks-net-0.3.3-SNAPSHOT.jar:0.3.3-SNAPSHOT] > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)