Hi,
Can you please help to see if there is any feature in HBase which will
satisfy following?
1) I need something which will be native to HBase and
2) Which will be able to execute some code at certain interval like daily
or weekly.
Is there any HBase feature which satisfies these two condition
Hi
My Hbase version is 1.0 running on mac, it seems a bug .
Just had to say, https://issues.apache.org/jira/browse/HBASE-13103 looks
*AWESOME*
On Thu, Jun 18, 2015 at 5:00 PM Mikhail Antonov
wrote:
> Yeah, I could see 2 reasons for remaining few regions to take
> unproportionally long time - 1) those regions are unproportionally
> large (you should be ab
Yeah, I could see 2 reasons for remaining few regions to take
unproportionally long time - 1) those regions are unproportionally
large (you should be able to quickly confirm it) and 2) they happened
to be hosted on really slow/overloaded machine(s). #1 seems far more
likely to me.
And as Nick said
actually, I found even when I try to create this table, it also failed with
it already exist! What does HBase check to see if a table already exist? I
did scan .META. , which also does not show this table.
hbase(main):009:0> list
TABLE
tsdb-uid
1 row(s) in 0.0100 seconds
hbase(main):010:0> crea
Hi,
I am trying to trying to clone a table from a snapshot, but it always fail
with below error. That table does not exist, although I was trying to clone
the same table, but failed. I feel that a reference to that table still
exist somewhere. Any hint what is going wrong?
Thanks
Tian-Ying
01
By looking at the master log, I think it failed because our table tsdb has
lots of empty region in the source cluster, and exportsnapshot does not
copy the empty folder over, so at the destination cluster, there are many
regions that don't have the column family folder, therefore caused error.
Now
If you're interested in region size balancing, please have a look at
https://issues.apache.org/jira/browse/HBASE-13103 . Please provide feedback
as we're hoping to have an early version available in 1.2.
Which reminds me, I owe Mikhail another review...
On Thu, Jun 18, 2015 at 9:39 AM, Elliott Cl
The balancer is not responsible fore region size decisions. The balancer is
only responsible for deciding which regionservers should host which regions.
Splits are determined by data size of a region. See max store file size.
On Thu, Jun 18, 2015 at 7:50 AM, Nasron Cheong wrote:
> Hi,
>
> I've n
Balancer distributes regions among RS's - not equalizes them. You,
probably, have very serious data skew and not optimal key design. I would
suggest you to try custom region split policy and provide your own split
key, because standard splitting algorithm does not work well.
On Jun 18, 2015 7:50 AM
Hi,
I've noticed there are two settings available when using the HBase balancer
(specifically the default stochastic balancer)
hbase.master.balancer.stochastic.tableSkewCost
hbase.master.loadbalance.bytable
How do these two settings relate? The documentation indicates when using
the stochastic
it sounds like a different version of jruby and/or jline is on your
classpath. Are you attempting to use HBase with anything else, for example
Apache Phoenix?
On Wed, Jun 17, 2015 at 6:23 PM, Arthur Chan
wrote:
> Hi,
>
>
> My compilation is successful, HBase-0.98.12.1
>
> [INFO]
> --
Btw, hbase 0.94.26 is on top of HDFS 2.5.0-chd5.3.2.
On Wed, Jun 17, 2015 at 10:41 AM, Neutron sharc
wrote:
> Hi community,
>
> I am testing the time to recovery of hbase 0.94.26. 0.94.26 can tolerate
> region server failures very smoothly. However, it seems client cannot
> recover when a
13 matches
Mail list logo