You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Denny Ye (Created) (JIRA)" <ji...@apache.org> on 2011/09/28 11:30:45 UTC
[jira] [Created] (HADOOP-7689) Process cannot exit when there is
many RPC readers more that actual client
Process cannot exit when there is many RPC readers more that actual client
--------------------------------------------------------------------------
Key: HADOOP-7689
URL: https://issues.apache.org/jira/browse/HADOOP-7689
Project: Hadoop Common
Issue Type: Bug
Components: ipc
Affects Versions: 0.21.0
Environment: local
Reporter: Denny Ye
I met a strange issue that process cannot exit when I run RPC test cases in my Eclipse.
Conditions:
1. Only one Server and one client(local)
2. I have set many readers(conf.setInt("ipc.server.read.threadpool.size", 5)), it great than client number.
After any test cases, the process cannot exit. I tested with several cases and found the root cause.
RPC serves socket with reader(transferring binary to Call), and even shutdown the thread pool. But all the free readers are blocked at "readSelector.select()" (they are useless by Listener)
Those threads and process cannot exit always.
It can be fixed by invoking corresponding selector for each reader.The same thing was done at 0.20 version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HADOOP-7689) Process cannot exit when there is
many RPC readers more that actual client
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237219#comment-13237219 ]
Hadoop QA commented on HADOOP-7689:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12517661/HADOOP-7689.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/761//console
This message is automatically generated.
> Process cannot exit when there is many RPC readers more that actual client
> --------------------------------------------------------------------------
>
> Key: HADOOP-7689
> URL: https://issues.apache.org/jira/browse/HADOOP-7689
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.21.0
> Environment: local
> Reporter: Denny Ye
> Labels: rpc
> Attachments: HADOOP-7689.patch
>
>
> I met a strange issue that process cannot exit when I run RPC test cases in my Eclipse.
> Conditions:
> 1. Only one Server and one client(local)
> 2. I have set many readers(conf.setInt("ipc.server.read.threadpool.size", 5)), it great than client number.
> After any test cases, the process cannot exit. I tested with several cases and found the root cause.
> RPC serves socket with reader(transferring binary to Call), and even shutdown the thread pool. But all the free readers are blocked at "readSelector.select()" (they are useless by Listener)
> Those threads and process cannot exit always.
> It can be fixed by invoking corresponding selector for each reader.The same thing was done at 0.20 version.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7689) Process cannot exit when there is
many RPC readers more that actual client
Posted by "Denny Ye (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denny Ye updated HADOOP-7689:
-----------------------------
Attachment: HADOOP-7689.patch
> Process cannot exit when there is many RPC readers more that actual client
> --------------------------------------------------------------------------
>
> Key: HADOOP-7689
> URL: https://issues.apache.org/jira/browse/HADOOP-7689
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.21.0
> Environment: local
> Reporter: Denny Ye
> Labels: rpc
> Attachments: HADOOP-7689.patch
>
>
> I met a strange issue that process cannot exit when I run RPC test cases in my Eclipse.
> Conditions:
> 1. Only one Server and one client(local)
> 2. I have set many readers(conf.setInt("ipc.server.read.threadpool.size", 5)), it great than client number.
> After any test cases, the process cannot exit. I tested with several cases and found the root cause.
> RPC serves socket with reader(transferring binary to Call), and even shutdown the thread pool. But all the free readers are blocked at "readSelector.select()" (they are useless by Listener)
> Those threads and process cannot exit always.
> It can be fixed by invoking corresponding selector for each reader.The same thing was done at 0.20 version.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7689) Process cannot exit when there is
many RPC readers more that actual client
Posted by "Denny Ye (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denny Ye updated HADOOP-7689:
-----------------------------
Status: Patch Available (was: Open)
> Process cannot exit when there is many RPC readers more that actual client
> --------------------------------------------------------------------------
>
> Key: HADOOP-7689
> URL: https://issues.apache.org/jira/browse/HADOOP-7689
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.21.0
> Environment: local
> Reporter: Denny Ye
> Labels: rpc
> Attachments: HADOOP-7689.patch
>
>
> I met a strange issue that process cannot exit when I run RPC test cases in my Eclipse.
> Conditions:
> 1. Only one Server and one client(local)
> 2. I have set many readers(conf.setInt("ipc.server.read.threadpool.size", 5)), it great than client number.
> After any test cases, the process cannot exit. I tested with several cases and found the root cause.
> RPC serves socket with reader(transferring binary to Call), and even shutdown the thread pool. But all the free readers are blocked at "readSelector.select()" (they are useless by Listener)
> Those threads and process cannot exit always.
> It can be fixed by invoking corresponding selector for each reader.The same thing was done at 0.20 version.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7689) Process cannot exit when there is
many RPC readers more that actual client
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated HADOOP-7689:
----------------------------
Environment: (was: local)
> Process cannot exit when there is many RPC readers more that actual client
> --------------------------------------------------------------------------
>
> Key: HADOOP-7689
> URL: https://issues.apache.org/jira/browse/HADOOP-7689
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.21.0
> Reporter: Denny Ye
> Labels: rpc
> Attachments: HADOOP-7689.patch
>
>
> I met a strange issue that process cannot exit when I run RPC test cases in my Eclipse.
> Conditions:
> 1. Only one Server and one client(local)
> 2. I have set many readers(conf.setInt("ipc.server.read.threadpool.size", 5)), it great than client number.
> After any test cases, the process cannot exit. I tested with several cases and found the root cause.
> RPC serves socket with reader(transferring binary to Call), and even shutdown the thread pool. But all the free readers are blocked at "readSelector.select()" (they are useless by Listener)
> Those threads and process cannot exit always.
> It can be fixed by invoking corresponding selector for each reader.The same thing was done at 0.20 version.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7689) Process cannot exit when there is
many RPC readers more that actual client
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated HADOOP-7689:
----------------------------
Tags: (was: rpc)
> Process cannot exit when there is many RPC readers more that actual client
> --------------------------------------------------------------------------
>
> Key: HADOOP-7689
> URL: https://issues.apache.org/jira/browse/HADOOP-7689
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.21.0
> Reporter: Denny Ye
> Labels: rpc
> Attachments: HADOOP-7689.patch
>
>
> I met a strange issue that process cannot exit when I run RPC test cases in my Eclipse.
> Conditions:
> 1. Only one Server and one client(local)
> 2. I have set many readers(conf.setInt("ipc.server.read.threadpool.size", 5)), it great than client number.
> After any test cases, the process cannot exit. I tested with several cases and found the root cause.
> RPC serves socket with reader(transferring binary to Call), and even shutdown the thread pool. But all the free readers are blocked at "readSelector.select()" (they are useless by Listener)
> Those threads and process cannot exit always.
> It can be fixed by invoking corresponding selector for each reader.The same thing was done at 0.20 version.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7689) Process cannot exit when there is
many RPC readers more that actual client
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated HADOOP-7689:
----------------------------
Status: Open (was: Patch Available)
Hi Denny - Can you rebase the patch for trunk if its still an issue? Also you mentioned hitting this in a test-case, so can we have a way to test this change as well, so that we don't regress it in future?
> Process cannot exit when there is many RPC readers more that actual client
> --------------------------------------------------------------------------
>
> Key: HADOOP-7689
> URL: https://issues.apache.org/jira/browse/HADOOP-7689
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.21.0
> Environment: local
> Reporter: Denny Ye
> Labels: rpc
> Attachments: HADOOP-7689.patch
>
>
> I met a strange issue that process cannot exit when I run RPC test cases in my Eclipse.
> Conditions:
> 1. Only one Server and one client(local)
> 2. I have set many readers(conf.setInt("ipc.server.read.threadpool.size", 5)), it great than client number.
> After any test cases, the process cannot exit. I tested with several cases and found the root cause.
> RPC serves socket with reader(transferring binary to Call), and even shutdown the thread pool. But all the free readers are blocked at "readSelector.select()" (they are useless by Listener)
> Those threads and process cannot exit always.
> It can be fixed by invoking corresponding selector for each reader.The same thing was done at 0.20 version.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira