Hi,
We recently ran into a production issue, here is the summary of events that
we went through, in timeline order:
1. One of the region servers went down (it became inaccessible)
2. Region transition initiated, some regions of multiple tables were
stuck in transition status. Most
I just created a new test table today, and when trying to drop it, I got
ERROR: No serverName in hbase:meta for
p_hashes,,1407880525015.6fe0bbb6e5a6f614891e7c1c5901c70f. containing
In the hbase master log, it said
client.HConnectionManager$HConnectionImplementation:
locateRegionInMeta failed;
Have you run hbck ?
Which release of hbase are you using ?
It would be helpful if you can search master log to see how p_hashes got
into this status.
Cheers
On Tue, Aug 12, 2014 at 4:24 PM, Thomas Kwan thomas.k...@manage.com wrote:
I just created a new test table today, and when trying to
Which version are you using?Try hbck and see if you find anything
interesting. This problem was faced by a couple of folks few weeks ago. Try
to search through the mailing list. Probably there is some problem with the
znode holding this table. Remove it and restart everything.
Warm Regards,
Tariq
try to diable table first
disable 'table_name'
drop 'tab-name'
On Thu, Jan 24, 2013 at 3:48 PM, hua beatls bea...@gmail.com wrote:
HI,
i have a table in 'transition' state, which couldn't be 'disable' or
enable. I try to 'drop' it but failed. below is the error messages.
Typically, hbck won't detect anything wrong here, as Ram said in another
thread we really should work in this functionality.
1.) Shut the HBase cluster - go to ZKcli and rmr /hbase - Start HBase back
up
2.) Move the table, use hbck -fixMeta -fixAssignments, restart the HBase
(not a great option
Sorry I should have specified those are different options to try, not an
ordered set of instructions.
On Thu, Jan 24, 2013 at 8:47 AM, Kevin O'dell kevin.od...@cloudera.comwrote:
Typically, hbck won't detect anything wrong here, as Ram said in another
thread we really should work in this
Normally you wouldn't need to remove the whole /hbase root on ZK. Removing
the node which is related to your table should be enough. Restart your
master so that it will read table state again, and you'll be able to drop
your ghost table.
On Thu, Jan 24, 2013 at 2:47 PM, Kevin O'dell
I am trying to drop one of the tables but on the shell I get run
major_compact. I have couple of questions:
1. How to see if this table has more than one region?
2. And why do I need to run major compact
hbase(main):010:0* drop 'SESSION_TIMELINE'
ERROR: Table SESSION_TIMELINE is enabled.
Hi Mohit,
You have the respons int your question ;)
Simple type:
major_compact .META.
On the shell.
To drop your table, just do:
disable 'SESSION_TIMELINE'
drop 'SESSION_TIMELINE'
--
JM
2012/7/23, Mohit Anchlia mohitanch...@gmail.com:
I am trying to drop one of the tables but on the shell
Hi Mohit,
A table must be disabled first in order to get deleted.
Regards,
Mohammad Tariq
On Tue, Jul 24, 2012 at 1:38 AM, Mohit Anchlia mohitanch...@gmail.com wrote:
I am trying to drop one of the tables but on the shell I get run
major_compact. I have couple of questions:
1. How
Thanks! but I am still trying to understand these 2 questions:
1. How to see if this table has more than one region?
2. And why do I need to run major compact if I have more than one region?
On Mon, Jul 23, 2012 at 1:14 PM, Mohammad Tariq donta...@gmail.com wrote:
Hi Mohit,
A table
1) http://URL_OF_YOUR_MASTER:60010/table.jsp?name=NAME_OF_YOUR_TABLE
will should you all the regions of your table.
2) I have no clue ;)
2012/7/23, Mohit Anchlia mohitanch...@gmail.com:
Thanks! but I am still trying to understand these 2 questions:
1. How to see if this table has more than one
You don't have to run the major compaction - the shell is doing that for
you. You must disable the table first, like:
disable 'session_timeline'
drop 'session_timeline'
See the admin.rb file:
def drop(table_name)
tableExists(table_name)
raise ArgumentError, Table #{table_name}
The HBase processes exposes a web-based user interface (in short UI),
which you can use to gain insight into the cluster's state, as well as
the tables it hosts. Just point your web browser to
http://hmaster:60010;. Although majority of the functionality is
read-only, but there are a few selected
Also, we don't have to worry about compaction under normal conditions.
When something is written to HBase, it is first written to an
in-memory store (memstore), once this memstore reaches a certain size,
it is flushed to disk into a store file (everything is also written
immediately to a log file
Thanks everyone for your help
On Mon, Jul 23, 2012 at 1:40 PM, Mohammad Tariq donta...@gmail.com wrote:
Also, we don't have to worry about compaction under normal conditions.
When something is written to HBase, it is first written to an
in-memory store (memstore), once this memstore reaches a
17 matches
Mail list logo
