[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

gendong1 updated ZOOKEEPER-4817:
--------------------------------
    Description: 
If the client connection is disconnected with zoo server, cancelledkeyexception 
will arise.

Here is a strange scenarios.

NIOServerCxn.doIO is blocked at line 333 by the fail-slow nic.

If the delay lasts more than 30s, cancelledkeyexception will disappear.

If the delay lasts for 25s, cancelledkeyexception will arise.

When the doIO encounters the slowdown caused by teh fail-slow nic, the context 
is same.

Are there any comments to figure out this issues? I will very appreciate them.

  was:
If the client connection is disconnected with zoo server, cancelledkeyexception 
will arise.

Here is a strange scenarios.

NIOServerCxn.doIO is blocked at line 333 by the fail-slow nic.

If the delay lasts more than 30s, cancelledkeyexception will disappear.

If the delay lasts for 25s, cancelledkeyexception will arise.

When the doIO encounters the slowdown caused by teh fail-slow nic, the context 
is same.


> CancelledKeyException does not work in some cases.
> --------------------------------------------------
>
>                 Key: ZOOKEEPER-4817
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4817
>             Project: ZooKeeper
>          Issue Type: Bug
>    Affects Versions: 3.10.0
>            Reporter: gendong1
>            Priority: Major
>         Attachments: node1-25.log, node1-60.log, node2-25.log, node2-60.log, 
> node3-25.log, node3-60.log
>
>
> If the client connection is disconnected with zoo server, 
> cancelledkeyexception will arise.
> Here is a strange scenarios.
> NIOServerCxn.doIO is blocked at line 333 by the fail-slow nic.
> If the delay lasts more than 30s, cancelledkeyexception will disappear.
> If the delay lasts for 25s, cancelledkeyexception will arise.
> When the doIO encounters the slowdown caused by teh fail-slow nic, the 
> context is same.
> Are there any comments to figure out this issues? I will very appreciate them.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to