[jira] [Commented] (HBASE-21753) Support getting the locations for all the replicas of a region

[beeshma (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-21753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748366#comment-16748366
 ] 

beeshma commented on HBASE-21753:
-

HI [~Apache9] , 

you mean  information's of Region server(Data-node) which have the particular 
Region ?

For Example ( input => Region R)

if dfs.replicaion =3 at hdfs-site.xml,  then three Region server information's 
output

 

 

 

> Support getting the locations for all the replicas of a region
> --
>
> Key: HBASE-21753
> URL: https://issues.apache.org/jira/browse/HBASE-21753
> Project: HBase
>  Issue Type: New Feature
>  Components: Client
>Reporter: Duo Zhang
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (HBASE-9556) Provide key range support to bulkload to avoid too many reducers even the data belongs to few regions

[beeshma (JIRA)]

[ 
https://issues.apache.org/jira/browse/HBASE-9556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15181788#comment-15181788
 ] 

beeshma commented on HBASE-9556:


How about  below logic to find start keys of regions?

HTable ht=new HTable(con,"test"); // Table object
NavigableMap np=ht.getRegionLocations();

Set setinfo=np.keySet();
List lis=new ArrayList();
lis.addAll(setinfo);
for(org.apache.hadoop.hbase.HRegionInfo h :lis)
{
System.out.println(h.getRegionId() + "getRegionId");

String s = new String(h.getStartKey());

System.out.println(s.toString()+"---start key");
}

Please suggest if anything wrong in this

> Provide key range support to bulkload to avoid too many reducers even the 
> data belongs to few regions
> -
>
> Key: HBASE-9556
> URL: https://issues.apache.org/jira/browse/HBASE-9556
> Project: HBase
>  Issue Type: Improvement
>  Components: mapreduce
>Reporter: rajeshbabu
>Assignee: rajeshbabu
>Priority: Minor
>
> Presently the number of reducers in bulk load are equal to number of regions.
> Lets suppose a table has 500 regions and import data only belongs 10 regions, 
> still we are starting 500(equal to no. of regions) reducers instead of 10. 
> Which will consume more time and resources. 
> If user knows the row key range of import data, then we can pass startkey 
> and/or endkey as input and based on the key range we can define the 
> partitions and number of reducers(regions to which the data belongs). This 
> helps to avoid too many reducers to start and do nothing and also avoids 
> contention in shuffling.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)