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 "Chris Nauroth (JIRA)" <ji...@apache.org> on 2013/06/30 19:37:20 UTC
[jira] [Resolved] (HADOOP-9674) RPC#Server#start does not block
until server is fully initialized and listening
[ https://issues.apache.org/jira/browse/HADOOP-9674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Nauroth resolved HADOOP-9674.
-----------------------------------
Resolution: Not A Problem
As per prior comments, this doesn't appear to be a real problem in practice, so I'm resolving it as not a problem.
> 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