cks of the HFile are stored across two different
> >> datanodes (hadoop-145 and hadoop-143).
> >>
> >> Let say a map task runs on hadoop-145 and needs to access the block 7.
> Then
> >> the map task needs to remotely access the block 7 on hadoop-143 server.
;> the map task needs to remotely access the block 7 on hadoop-143 server.
>> Almost half of the data blocks are stored & accessed remotely. Referring
>> from the above example, It's hard to say that the data locality is being
>> applied to HBase.
>>
>>
e:
>
>> Hi Ben,
>>
>> See inline...
>>
>> On Jun 15, 2012, at 6:56 AM, Ben Kim wrote:
>>
>>> Hi,
>>>
>>> I've been posting questions in the mailing-list quiet often lately, and
>>> here goes another one about d
the mailing-list quiet often lately, and
> > here goes another one about data locality
> > I read the excellent blog post about data locality that Lars George wrote
> > at http://www.larsgeorge.com/2010/05/hbase-file-locality-in-hdfs.html
> >
> > I understand data locali
Ben Kim wrote:
>
> > Hi,
> >
> > I've been posting questions in the mailing-list quiet often lately, and
> > here goes another one about data locality
> > I read the excellent blog post about data locality that Lars George wrote
> > at http://www.lar
orge wrote
> at http://www.larsgeorge.com/2010/05/hbase-file-locality-in-hdfs.html
>
> I understand data locality in hbase as locating a region in a region-server
> where most of its data blocks reside.
The opposite is happening, i.e. the region server process triggers for all data
it writes to
Hi,
I've been posting questions in the mailing-list quiet often lately, and
here goes another one about data locality
I read the excellent blog post about data locality that Lars George wrote
at http://www.larsgeorge.com/2010/05/hbase-file-locality-in-hdfs.html
I understand data locali
