[
https://issues.apache.org/jira/browse/HBASE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638689#action_12638689
]
stack commented on HBASE-919:
-----------------------------
This issue was uncovered because of way HMaster now refuses to let out the root
location till all regions deployed? HBASE-918?
Would there ever be functionality in HTable that is not in HConnectionManager
regards retries or table-level manipulations that an HMaster or an HRS might
exploit?
> Master and Region Server should not use HTable
> ----------------------------------------------
>
> Key: HBASE-919
> URL: https://issues.apache.org/jira/browse/HBASE-919
> Project: Hadoop HBase
> Issue Type: Sub-task
> Components: master, regionserver
> Affects Versions: 0.18.0
> Reporter: Jim Kellerman
> Assignee: Jim Kellerman
> Priority: Blocker
> Fix For: 0.18.1, 0.19.0
>
>
> The master and region servers should NEVER use a HTable. HTable is only for
> client side use. During cluster startup, for example, there is not enough
> initialized for an HTable to work in either the master or a region server.
> The master and region server should therefore only use HConnectionManager and
> even there should only use very basic operations like getHRegionConnection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
