Akmal:
When 0.98.13 is released later this month, you can upgrade to 0.98.13 with
rolling upgrade.
Cheers
On Tue, May 5, 2015 at 6:28 AM, Akmal Abbasov akmal.abba...@icloud.com
wrote:
Hi Sean,
Thank you for a quick reply.
I am not sure about next upgrade time for now.
So the only solution
Hi Akmal,
Unfortunately there is not. Right now that feature is only slated for HBase
2.0 IIRC, but we should be able to get it into an earlier version. I'll
open a backport JIRA.
Do you know when you'll be able to upgrade next?
--
Sean
On May 5, 2015 4:18 AM, Akmal Abbasov
Hi Sean,
Thank you for a quick reply.
I am not sure about next upgrade time for now.
So the only solution in that case would be to parse the output of the HBase
shell command?
Thank you.
Regards,
Akmal Abbasov
On 05 May 2015, at 15:25, Sean Busbey bus...@cloudera.com wrote:
Hi Akmal,
On Tue, May 5, 2015 at 8:58 AM, Bryan Beaudreault bbeaudrea...@hubspot.com
wrote:
Hello,
I'm about to start tackling our upgrade path for 0.94 to 1.0+. We have 6
production hbase clusters, 2 hadoop clusters, and hundreds of
APIs/daemons/crons/etc hitting all of these things. Many of these
Thanks for the response guys!
You've done a review of HTI in 1.0 vs 0.94 to make sure we've not
mistakenly dropped anything you need? (I see that stuff has moved around
but HTI should have everything still from 0.94)
Yea, so far so good for HTI features.
Sounds like you have experience
If we're extending the vote I can find time to verify if running against
2.2 after using our default build fails. So long as running works, I think
we can just release note the build problem for now.
If running fails I'd vote for sinking, given how easy a fix is.
--
Sean
On May 5, 2015 4:17 PM,
So what's the conclusion here? Are we dropping 2.2 support or updating the
poms and sinking the RC?
On Fri, May 1, 2015 at 7:47 AM, Sean Busbey bus...@cloudera.com wrote:
On Thu, Apr 30, 2015 at 6:48 PM, Andrew Purtell apurt...@apache.org
wrote:
We could patch our POMs to reference the
Just to a little bit to what StAck said:
--
Cloudera, Inc.
On Tue, May 5, 2015 at 3:53 PM, Stack st...@duboce.net wrote:
On Tue, May 5, 2015 at 8:58 AM, Bryan Beaudreault
bbeaudrea...@hubspot.com
wrote:
Hello,
I'm about to start tackling our upgrade path for 0.94 to 1.0+. We have 6
Thank you for your response!
So I guess 'salt' is a bit of a misnomer. What I used to do is this :
1) Say that my key value is something like '1234foobar'
2) I obtain the hash of '1234foobar'. Let's say that's '54824923'
3) I mod the hash by my number of regions. Let's say I have 2000
Hello,
I'm about to start tackling our upgrade path for 0.94 to 1.0+. We have 6
production hbase clusters, 2 hadoop clusters, and hundreds of
APIs/daemons/crons/etc hitting all of these things. Many of these clients
hit multiple clusters in the same process. Daunting to say the least.
We can't
Yes, currently that's what some of our in-house tooling did. Basically you
grep for the word ERROR. It is error-prone and brittle to say the least. :/
On Tue, May 5, 2015 at 6:28 AM, Akmal Abbasov akmal.abba...@icloud.com
wrote:
Hi Sean,
Thank you for a quick reply.
I am not sure about next
we do this for almost all our tables
On May 5, 2015 11:05 AM, jeremy p athomewithagroove...@gmail.com wrote:
Thank you for your response!
So I guess 'salt' is a bit of a misnomer. What I used to do is this :
1) Say that my key value is something like '1234foobar'
2) I obtain the hash of
I'm not sure what's going on with this. I'm in contact with Infra about the
issue.
On Tue, May 5, 2015 at 12:00 AM, Enis Söztutar enis@gmail.com wrote:
Ok, I am able to verify with that KEY file. Did you update your key at
id.apache.org? There is a bot that updates the key under
Ok, I am able to verify with that KEY file. Did you update your key at
id.apache.org? There is a bot that updates the key under people.apache.org
as far as I remember.
Enis
On Mon, May 4, 2015 at 8:36 PM, Nick Dimiduk ndimi...@apache.org wrote:
I had uploaded to subkeys.pgp.net originally,
Dear all,
In the hbase-default.xml, description about hbase.hregion.memstore.flush.size
is following: Memstore will be flushed to disk if size of the memstore exceeds
this number of bytes. Value is checked by a thread that runs every
hbase.server.thread.wakefrequency. However, in the source
Hi Lars,
Regarding region sizes - it was kinda conclusion we got after reading bunch
of articles trying to figure out what optimal region and memstore size for
us would be in the process of migrating from 'old' cluster which was under
very high load to this new and more performant one. Trying to
Hello Gaby,
I don't think we have done any testing from HBase 1.0 clients to HBase 0.98
servers to cover any possible performance regressions when using a newer
version on the client side. However the general practice is to upgrade
first your servers and then upgrade clients to the newer version
Hello,
I have a question on using a newer version of HBase client against older
version of HBase servers.
Specifically, does HBase client 1.0.0 work with HBase server 0.98.6? Is
there any performance
implications?
Thanks,
Gaby
Yes, what you described mod(hash(rowkey),n) where n is the number of regions
will remove the hotspotting issue.
However, if your key is sequential you will only have regions half full post
region split.
Look at it this way…
If I have a key that is a sequential count 1,2,3,4,5 … I am
Silly question…
How much memory do you have on your machine and how much do you allocate to
HBase?
More to the point, how much memory is allocated to your memstore?
Suppose you have maxfilesize set to 100GB and your memstore is only 1GB in
size. (round numbers to make the math easier…)
If
Due to infrastructure issues on my side, I've not been able to test this RC
as thoroughly as I'd like. Given this and the pending HBaseCon, I'd like to
extend the voting window. The expiration time is now midnight/Pacific on
Sunday, May 10.
Thanks everyone for your time on testing.
Nick
On Wed,
Hi,
HBASE-11658 https://issues.apache.org/jira/browse/HBASE-11658 adds a non
interactive mode to HBase shell and return modes depending on the success or
failure.
But, I am using HBase hbase-0.98.7-hadoop2, which doesn’t have this feature. So
is there any way for checking the result of the
22 matches
Mail list logo