[
https://issues.apache.org/jira/browse/HBASE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568637#action_12568637
]
Jim Kellerman commented on HBASE-55:
------------------------------------
I disagree with the statement "at no point does it make sense for a region
server to "say no" to an assignment" for one particular case: If the region
server's open queue gets too deep it will not be able to open the region before
the master times out the assignment and assigns the region to another server
anyway. When this happens, the original server finally gets the region open,
reports to master and master says "close it, I've already assigned it
elsewhere" in this case, two region servers can be messing with the region's
files which could potentially corrupt the region.
> [hbase] Improve Master region assignment function
> -------------------------------------------------
>
> Key: HBASE-55
> URL: https://issues.apache.org/jira/browse/HBASE-55
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Bryan Duxbury
> Fix For: 0.2.0
>
>
> We would like the master's region assignment function to take into account
> more factors when choosing where to assign regions.
>
> - More advanced accounting of load on regionserver - memory, # requests, etc
> - Don't deploy both daughter regions to the same regionserver
> - Assign regions where the underlying DFS blocks are hosted if possible
> Please add additional ideas in comments as they come up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
