[
https://issues.apache.org/jira/browse/HBASE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923573#action_12923573
]
stack commented on HBASE-3141:
------------------------------
This looks like an issue Todd was playing with a while back where RS hosting
.META. would connect to itself to get data from .META. before RPC had been put
up. He put up a sketch patch over here
http://github.com/toddlipcon/hbase/commit/c1236fca54e25c36561d428b6755a950ca1c208f.
In it, he introduces a flag in rpc server that is set true when rpc has
started. When false, throws exceptions "Not Yet Accepting Connections".
Lets make a test that this is actually an issue. Maybe the early rpc is just
handled post listener/responder startup?
> Master RPC server needs to be started before an RS can check in
> ---------------------------------------------------------------
>
> Key: HBASE-3141
> URL: https://issues.apache.org/jira/browse/HBASE-3141
> Project: HBase
> Issue Type: Bug
> Components: master
> Reporter: Jonathan Gray
> Priority: Critical
> Fix For: 0.90.0
>
>
> Starting up an RPC server is done in two steps. In the constructor, we
> instantiate the RPC server. Then in startServiceThreads() we start() it.
> If someone RPCs in between the instantiation and the start(), it seems that
> bad things can happen. We need to make sure this can't happen and there
> aren't any races here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
