I am a veggie ^_^
That's a slogan; It urges people to eat more veggetables on Monday for
saving our planet.
Fleming Chiu(邱宏明)
707-6128
y_823...@tsmc.com
週一無肉日吃素救地球(Meat Free Monday Taiwan)
saint....@gmail.c
om To:
hbase-user@hadoop.apache.org
Sent by: cc: (bcc: Y_823910/TSMC)
saint....@gmail.c Subject: Re: could not be
reached after 1 tries
om
2010/03/31 01:39
PM
Please respond to
hbase-user
If you are still on HBase version : 0.20.2, r834515, you should
update. There are a few NPE fixes in 0.20.3 and if I look at the code
in the branch around where you are getting the NPE below, its got lots
of protections against what you are seeing below.
> 週一無肉日吃素救地球(Meat Free Monday Taiwan)
What is the above about?
Thanks,
St.Ack
2010/3/30 <y_823...@tsmc.com>:
> I found an error in the log.
>
> 2010-03-30 10:10:32,135 ERROR
> org.apache.hadoop.hbase.regionserver.HRegionServer:
> java.lang.NullPointerException
> 2010-03-30 10:10:32,136 INFO org.apache.hadoop.ipc.HBaseServer: IPC
Server
> handler 45 on 60020, call delete([...@7a914631,
> row=N900W06LS10000110_810593676N900W06LS1000011, ts=9223372036854775807,
> families={}) from 10.81.47.36:41022: error: java.io.IOException:
> java.lang.NullPointerException
> java.io.IOException: java.lang.NullPointerException
> at
>
org.apache.hadoop.hbase.regionserver.HRegionServer.convertThrowableToIOE(HRegionServer.java:869)
> at
>
org.apache.hadoop.hbase.regionserver.HRegionServer.convertThrowableToIOE(HRegionServer.java:859)
> at
>
org.apache.hadoop.hbase.regionserver.HRegionServer.delete(HRegionServer.java:2028)
> at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:648)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:915)
> Caused by: java.lang.NullPointerException
>
>
> Fleming Chiu(邱宏明)
> 707-6128
> y_823...@tsmc.com
> 週一無肉日吃素救地球(Meat Free Monday Taiwan)
>
>
>
>
>
> saint....@gmail.c
> om To:
hbase-user@hadoop.apache.org
> Sent by: cc: (bcc:
Y_823910/TSMC)
> saint....@gmail.c Subject: Re: could not be
reached after 1 tries
> om
>
>
> 2010/03/31 12:15
> AM
> Please respond to
> hbase-user
>
>
>
>
>
>
> Well, what do the logs tell about that servers state?
> St>Ack
>
> 2010/3/30 <y_823...@tsmc.com>:
>> Was it busy at the time the client was trying to access it? No
>>
>> Do subsequent accesses to this regionserver work? No
>> Showing that message all the time.
>>
>> Thanks
>>
>>
>> Fleming Chiu(邱宏明)
>> 707-6128
>> y_823...@tsmc.com
>> 週一無肉日吃素救地球(Meat Free Monday Taiwan)
>>
>>
>>
>>
>>
>> saint....@gmail.c
>> om To:
> hbase-user@hadoop.apache.org
>> Sent by: cc: (bcc:
> Y_823910/TSMC)
>> saint....@gmail.c Subject: Re: could not be
> reached after 1 tries
>> om
>>
>>
>> 2010/03/30 03:44
>> PM
>> Please respond to
>> hbase-user
>>
>>
>>
>>
>>
>>
>> Was it busy at the time the client was trying to access it? Do
>> subsequent accesses to this regionserver work?
>> St.Ack
>>
>> 2010/3/29 <y_823...@tsmc.com>:
>>> Hi,
>>>
>>> One of my region server is still listed on the webpage Region Server,
> but
>>> it raised folloing message while running my program.
>>> 10/03/30 13:11:18 INFO ipc.HbaseRPC: Server at /10.81.47.43:60020 could
>> not
>>> be reached after 1 tries, giving up
>>> Any suggestion?
>>>
>>>
>>> Fleming Chiu(邱宏明)
>>> 707-6128
>>> y_823...@tsmc.com
>>> 週一無肉日吃素救地球(Meat Free Monday Taiwan)
>>>
>>>
>>>
>>>
>>>
>>> john smith
>>> <js1987.sm...@gma To:
>> hbase-user@hadoop.apache.org
>>> il.com> cc: (bcc:
>> Y_823910/TSMC)
>>> Subject: Re: Region
>> assignment in Hbase
>>> 2010/03/30 10:49
>>> AM
>>> Please respond to
>>> hbase-user
>>>
>>>
>>>
>>>
>>>
>>>
>>> J-D thanks for your reply. I have some doubts which I posted inline .
>>> Kindly
>>> help me
>>>
>>> On Tue, Mar 30, 2010 at 2:23 AM, Jean-Daniel Cryans
>>> <jdcry...@apache.org>wrote:
>>>
>>>> Inline.
>>>>
>>>> J-D
>>>>
>>>> On Mon, Mar 29, 2010 at 11:45 AM, john smith <js1987.sm...@gmail.com>
>>>> wrote:
>>>> > Hi all,
>>>> >
>>>> > I read the issue HBase-57 (
>>>> https://issues.apache.org/jira/browse/HBASE-57 )
>>>> > . I don't really understand the use of assigning regions keeping DFS
>> in
>>>> > mind. Can anyone give an example usecase showing its advantages
>>>>
>>>> A region is composed of files, files are composed of blocks. To read
>>>> data, you need to fetch those blocks. In HDFS you normally have access
>>>> to 3 replicas and you fetch one of them over the network. If one of
>>>> the replica is on the local datanode, you don't need to go through the
>>>> network. This means less network traffic and better response time.
>>>>
>>>
>>> Is this the scenario that occurs for catering the read requests? In
the
>>> thread "Data distribution in HBase" , one of the people mentioned that
>> the
>>> data hosted by the Region Server may not actually reside on the same
>>> machine
>>> . So when asked for data , it fetches from the system containing the
>> data.
>>> Am I right? Why is the data hosted by a "Region Server" doesn't lie on
>> the
>>> same machine . Doesn't the name name "Region Server" imply that it
holds
>>> all
>>> the regions it contains? Is it due to splits or restarting the HBase ?
>>>
>>>
>>>>
>>>> > Can
>>>> > map-reduce exploit it's advantage in any way (if data is distributed
>> in
>>>> the
>>>> > above manner) or is it just the read-write performance that gets
>>>> improved .
>>>>
>>>> MapReduce works in the exact same way, it always tries to put the
>>>> computation next to where the data is. I recommend reading the
>>>> MapReduce tutorial
>>>> http://hadoop.apache.org/common/docs/r0.20.0
>>> /mapred_tutorial.html#Overview
>>>>
>>>
>>> Also the same case Applies here I guess . When a map is run on a Region
>>> Server, It's data may not actually lie on the same machine . So it
>> fetches
>>> from the machine containing it. This reduces the data locality !
>>>
>>>
>>>>
>>>> > Can some one please help me in understanding this.
>>>> >
>>>> > Regards
>>>> > JS
>>>> >
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>
---------------------------------------------------------------------------
>>> TSMC PROPERTY
>>> This email communication (and any attachments) is proprietary
>> information
>>> for the sole use of its
>>> intended recipient. Any unauthorized review, use or distribution by
>> anyone
>>> other than the intended
>>> recipient is strictly prohibited. If you are not the intended
>> recipient,
>>> please notify the sender by
>>> replying to this email, and then delete this email and any copies of
it
>>> immediately. Thank you.
>>>
>>
>
---------------------------------------------------------------------------
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
---------------------------------------------------------------------------
>> TSMC PROPERTY
>> This email communication (and any attachments) is proprietary
> information
>> for the sole use of its
>> intended recipient. Any unauthorized review, use or distribution by
> anyone
>> other than the intended
>> recipient is strictly prohibited. If you are not the intended
> recipient,
>> please notify the sender by
>> replying to this email, and then delete this email and any copies of it
>> immediately. Thank you.
>>
>
---------------------------------------------------------------------------
>>
>>
>>
>>
>
>
>
>
>
---------------------------------------------------------------------------
> TSMC PROPERTY
> This email communication (and any attachments) is proprietary
information
> for the sole use of its
> intended recipient. Any unauthorized review, use or distribution by
anyone
> other than the intended
> recipient is strictly prohibited. If you are not the intended
recipient,
> please notify the sender by
> replying to this email, and then delete this email and any copies of it
> immediately. Thank you.
>
---------------------------------------------------------------------------
>
>
>
>
---------------------------------------------------------------------------
TSMC PROPERTY
This email communication (and any attachments) is proprietary information
for the sole use of its
intended recipient. Any unauthorized review, use or distribution by anyone
other than the intended
recipient is strictly prohibited. If you are not the intended recipient,
please notify the sender by
replying to this email, and then delete this email and any copies of it
immediately. Thank you.
---------------------------------------------------------------------------
