wrote:
Hi
We are running hbase 0.94.6 cdh 4.4 and have a problem with one table
not
being assigned to any region. This is the SYSTEM.TABLE in Phoenix so
all
tables are basically non functional at the moment.
When running hbck repair we get the following...
ERROR
Hi
We are running hbase 0.94.6 cdh 4.4 and have a problem with one table not
being assigned to any region. This is the SYSTEM.TABLE in Phoenix so all
tables are basically non functional at the moment.
When running hbck repair we get the following...
ERROR: Region { meta =
SYSTEM.TABLE
...@gmail.com
wrote:
Hi
We are running hbase 0.94.6 cdh 4.4 and have a problem with one table not
being assigned to any region. This is the SYSTEM.TABLE in Phoenix so all
tables are basically non functional at the moment.
When running hbck repair we get the following...
ERROR: Region { meta
not
being assigned to any region. This is the SYSTEM.TABLE in Phoenix so all
tables are basically non functional at the moment.
When running hbck repair we get the following...
ERROR: Region { meta =
SYSTEM.TABLE,,1385477659546.b739cf1ef14dd664ae873bf5b16e7a35., hdfs =
hdfs://primecluster
are running hbase 0.94.6 cdh 4.4 and have a problem with one table not
being assigned to any region. This is the SYSTEM.TABLE in Phoenix so all
tables are basically non functional at the moment.
When running hbck repair we get the following...
ERROR: Region { meta =
SYSTEM.TABLE,,1385477659546
Hi St.Ack,
removing the zookeeper data dir did the trick. The master stopped again
after complaining that it couldn't resolve the old node name (which I
was only able to grep under the dfs data - any idea why the master host
name is persisted there and read again?) but defining that as a
On Thu, Jan 19, 2012 at 1:31 AM, Henning Blohm henning.bl...@zfabrik.dewrote:
removing the zookeeper data dir did the trick. The master stopped again
after complaining that it couldn't resolve the old node name (which I was
only able to grep under the dfs data - any idea why the master host
re: We should do same (smile)
I added a section in Troubleshooting/builtin tools for the 'zkcli' utility
earlier this week (not on website, but book is updated).
I agree that particular situation deserves a use-case in Troubleshooting.
On 1/19/12 12:08 PM, Stack st...@duboce.net wrote:
On
On 01/19/2012 06:08 PM, Stack wrote:
On Thu, Jan 19, 2012 at 1:31 AM, Henning Blohmhenning.bl...@zfabrik.dewrote:
removing the zookeeper data dir did the trick. The master stopped again
after complaining that it couldn't resolve the old node name (which I was
only able to grep under the dfs
Hi,
After an upgrade of hadoop and hbase (to 0.90.4-cdh3u2) from 0.90 hbase
and 0.20-append hadoop on a single node test installation everything
worked fine initially.
Then there was some DNS changes and host name changes which resulted in
a lot hostname oldname cannot be resolved problems
On Tue, Jan 17, 2012 at 7:19 AM, Henning Blohm henning.bl...@zfabrik.de wrote:
Hi,
After an upgrade of hadoop and hbase (to 0.90.4-cdh3u2) from 0.90 hbase and
0.20-append hadoop on a single node test installation everything worked fine
initially.
Would suggest you go to 0.90.5 while you are
org.apache.hadoop.hbase.master.AssignmentManager:
Overwriting 612342de1fe4733f72299d70addb6d11 on
serverName=167-6-1-11,20020,1308105402003, load=(requests=0, regions=0,
usedHeap=0, maxHeap=0)
3.Region was assigned to this dead RS at 10:50:20,671:
10:50:20,671 DEBUG
org.apache.hadoop.hbase.master.AssignmentManager:
Overwriting 612342de1fe4733f72299d70addb6d11 on
serverName=167-6-1-11,20020,1308105402003, load=(requests=0, regions=0,
usedHeap=0, maxHeap=0)
3.Region was assigned to this dead RS at 10:50:20,671:
10:50:20,671 DEBUG
of
AssignmentManager#regions:
10:45:55,081 WARN org.apache.hadoop.hbase.master.AssignmentManager: Overwriting
612342de1fe4733f72299d70addb6d11 on serverName=167-6-1-11,20020,1308105402003,
load=(requests=0, regions=0, usedHeap=0, maxHeap=0)
3.Region was assigned to this dead RS at 10:50:20,671:
10
612342de1fe4733f72299d70addb6d11 on
serverName=167-6-1-11,20020,1308105402003, load=(requests=0, regions=0,
usedHeap=0, maxHeap=0)
3.Region was assigned to this dead RS at 10:50:20,671:
10:50:20,671 DEBUG org.apache.hadoop.hbase.master.AssignmentManager:
Assigning region
:
10:45:55,081 WARN org.apache.hadoop.hbase.master.AssignmentManager:
Overwriting 612342de1fe4733f72299d70addb6d11 on
serverName=167-6-1-11,20020,1308105402003, load=(requests=0, regions=0,
usedHeap=0, maxHeap=0)
3.Region was assigned to this dead RS at 10:50:20,671:
10:50:20,671 DEBUG
16 matches
Mail list logo