hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-8958) Sometimes we refer to the single .META. table region as ".META.,,1" and other times as ".META.,,1.1028785192"
Date Fri, 02 Aug 2013 19:41:48 GMT

     [ https://issues.apache.org/jira/browse/HBASE-8958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-8958:
-------------------------

    Fix Version/s:     (was: 0.95.2)

Not the end of the world and workaround.  Moving out.
                
> Sometimes we refer to the single .META. table region as ".META.,,1" and other times as
".META.,,1.1028785192" 
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8958
>                 URL: https://issues.apache.org/jira/browse/HBASE-8958
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>
> See here how we say in a log:
> {code}
> 2013-07-15 22:32:53,805 INFO  [main] regionserver.HRegion(4176): Open {ENCODED =>
1028785192, NAME => '.META.,,1', STARTKEY => '', ENDKEY => ''}
> {code}
> but when we open other regions we do:
> {code}
> 764 2013-07-15 22:40:10,867 INFO  [RS_OPEN_REGION-durruti:61987-0] regionserver.HRegion:
Open {ENCODED => 93dad2bbf6ff5ea0d7477f504b303346, NAME => 'x,,1373953210791.93dad2bbf6ff5ea0d7477f504b303346.',
...
> {code}
> Note how in the second, the name includes the encoded name.
> We'll also do :
> {code}
> 2013-07-15 22:32:53,810 INFO  [main] regionserver.HRegion(629): Onlined 1028785192/.META.;
next sequenceid=1
> {code}
> vs
> {code}
> 785 2013-07-15 22:40:10,885 INFO  [AM.ZK.Worker-pool-2-thread-7] master.RegionStates:
Onlined 93dad2bbf6ff5ea0d7477f504b303346 on durruti,61987,1373947581222
> {code}
> ... where we print the encoded name.
> Master web UI shows ".META.,,1.1028785192"
> Benoit originally noticed this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message