hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HADOOP-9674) RPC#Server#start does not block until server is fully initialized and listening
Date Sun, 30 Jun 2013 17:37:20 GMT

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

Chris Nauroth reassigned HADOOP-9674:
-------------------------------------

    Assignee: Chris Nauroth
    
> RPC#Server#start does not block until server is fully initialized and listening
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-9674
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9674
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 3.0.0, 2.2.0
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>
> This problem was originally mentioned in discussion on HADOOP-8980.  When calling {{RPC#Server#start}},
initialization of the server's internal {{Listener}} and {{Reader}} threads happens in the
background.  This initialization is not guaranteed to complete by the time the caller returns
from {{RPC#Server#start}}.  This may be misleading to a caller that expects the server has
been fully initialized.  This problem sometimes manifests as a test failure in {{TestRPC#testStopsAllThreads}}.
 This test looks at the stack frames of all running threads, expecting to find the {{Listener}}
and {{Reader}} threads, but sometimes it doesn't find them.

--
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

Mime
View raw message