[
https://issues.apache.org/jira/browse/HBASE-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021967#comment-13021967
]
Ted Yu commented on HBASE-3779:
-------------------------------
I tested patch version 2 on our staging cluster. It works:
{code}
2011-04-20 05:09:48,328 INFO org.apache.hadoop.hbase.master.AssignmentManager:
placing REGION => {NAME =>
'GRID-GRIDSQL-STAGING-THREEGPPSPEECHCALLS-1303255874782,69812FFB7A81D555FE61CA80130A81B5,1303276182555.79c4ba0610797cfdadec17c14a692a59.',
STARTKEY => '69812FFB7A81D555FE61CA80130A81B5', ENDKEY =>
'6V\xBEp\xAA\xFF@\x0Fs\xE8\x91\x12\xB1zc\xB4\xB7\xF5\x87Y\xFC\x02}\xA1F\x8A\x97\x8D\xD5\x1F\xA7\xB8',
... on serverName=us01-ciqps1-grid07.carrieriq.com,60020,1303275849244,
load=(requests=0, regions=325, usedHeap=23, maxHeap=3973) from
serverName=us01-ciqps1-grid02.carrieriq.com,60020,1303275849713,
load=(requests=0, regions=341, usedHeap=2118, maxHeap=3973)
{code}
>From table.jsp, I verified that the above region was indeed on grid07.
> Allow split regions to be placed on different region servers
> ------------------------------------------------------------
>
> Key: HBASE-3779
> URL: https://issues.apache.org/jira/browse/HBASE-3779
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 0.90.2
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 3779-v2.patch
>
>
> Currently daughter regions are placed on the same region server where the
> parent region was.
> Stanislav Barton mentioned the idea that load information should be
> considered when placing the daughter regions.
> The rationale is that the daughter regions tend to receive more writes. So it
> would be beneficial to place at least one daughter region on a different
> region server.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
