[
https://issues.apache.org/jira/browse/HBASE-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Gray updated HBASE-3141:
---------------------------------
Attachment: HBASE-3141-v1.patch
Patch moves start of service threads to before we put up cluster up flag. This
kind of deals with this issue.
I think real fix is for RPC server to properly handle/reject any requests when
it's in a weird state between construction and starting.
> 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
>
> Attachments: HBASE-3141-v1.patch
>
>
> 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.
