zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-832) Invalid session id causes infinite loop during automatic reconnect
Date Sun, 08 Nov 2015 21:27:11 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995817#comment-14995817

Hadoop QA commented on ZOOKEEPER-832:

+1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 1712218.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 2 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 2.0.3) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2948//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2948//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2948//console

This message is automatically generated.

> Invalid session id causes infinite loop during automatic reconnect
> ------------------------------------------------------------------
>                 Key: ZOOKEEPER-832
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-832
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.4.5, 3.5.0
>         Environment: All
>            Reporter: Ryan Holmes
>            Assignee: Arshad Mohammad
>            Priority: Critical
>             Fix For: 3.4.8, 3.5.2, 3.6.0
>         Attachments: ZOOKEEPER-832.patch, ZOOKEEPER-832.patch, ZOOKEEPER-832.patch, ZOOKEEPER-832.patch,
ZOOKEEPER-832.patch, ZOOKEEPER-832.patch, ZOOKEEPER-832.patch, ZOOKEEPER-832.patch, ZOOKEEPER-832.patch,
> Steps to reproduce:
> 1.) Connect to a standalone server using the Java client.
> 2.) Stop the server.
> 3.) Delete the contents of the data directory (i.e. the persisted session data).
> 4.) Start the server.
> The client now automatically tries to reconnect but the server refuses the connection
because the session id is invalid. The client and server are now in an infinite loop of attempted
and rejected connections. While this situation represents a catastrophic failure and the current
behavior is not incorrect, it appears that there is no way to detect this situation on the
client and therefore no way to recover.
> The suggested improvement is to send an event to the default watcher indicating that
the current state is "session invalid", similar to how the "session expired" state is handled.
> Server log output (repeats indefinitely):
> 2010-08-05 11:48:08,283 - INFO  [NIOServerCxn.Factory:$Factory@250]
- Accepted socket connection from /
> 2010-08-05 11:48:08,284 - INFO  [NIOServerCxn.Factory:]
- Refusing session request for client / as it has seen zxid 0x44 our last zxid
is 0x0 client must try another server
> 2010-08-05 11:48:08,284 - INFO  [NIOServerCxn.Factory:]
- Closed socket connection for client / (no session established for client)
> Client log output (repeats indefinitely):
> 11:47:17 org.apache.zookeeper.ClientCnxn startConnect INFO line 1000 - Opening socket
connection to server localhost/
> 11:47:17 org.apache.zookeeper.ClientCnxn run WARN line 1120 - Session 0x12a3ae4e893000a
for server null, unexpected error, closing socket connection and attempting reconnect
> java.net.ConnectException: Connection refused
> 	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> 	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:574)
> 	at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1078)
> 11:47:17 org.apache.zookeeper.ClientCnxn cleanup DEBUG line 1167 - Ignoring exception
during shutdown input
> java.nio.channels.ClosedChannelException
> 	at sun.nio.ch.SocketChannelImpl.shutdownInput(SocketChannelImpl.java:638)
> 	at sun.nio.ch.SocketAdaptor.shutdownInput(SocketAdaptor.java:360)
> 	at org.apache.zookeeper.ClientCnxn$SendThread.cleanup(ClientCnxn.java:1164)
> 	at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1129)
> 11:47:17 org.apache.zookeeper.ClientCnxn cleanup DEBUG line 1174 - Ignoring exception
during shutdown output
> java.nio.channels.ClosedChannelException
> 	at sun.nio.ch.SocketChannelImpl.shutdownOutput(SocketChannelImpl.java:649)
> 	at sun.nio.ch.SocketAdaptor.shutdownOutput(SocketAdaptor.java:368)
> 	at org.apache.zookeeper.ClientCnxn$SendThread.cleanup(ClientCnxn.java:1171)
> 	at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1129)

This message was sent by Atlassian JIRA

View raw message