Drat, you're right.
HBASE-8656 was pulled last minute, and it seems I forgot to recut the tag.
Will do that now (means I need to re-release to maven as well :( )
Thanks for pointing that out.
-- Lars
From: Aditya
To: "dev@hbase.apache.org" ; lars hofhansl
Cc
Fixed the tags. Need to figure out how to fix up the maven release.
From: Aditya
To: "dev@hbase.apache.org" ; lars hofhansl
Cc: hbase-user
Sent: Friday, July 5, 2013 9:12 PM
Subject: Re: [ANNOUNCE] HBase 0.94.9 is available for download
Thanks Lars.
So I cannot fix the maven release after the fact. So we have the following
options:
1. Leave it as is. Tags/tar have HBASE-8656, but the maven release misses that
that one fix; and release 0.94.10 soon.
2. Release 0.94.9.1, which would be identical to 0.94.9 (except for the release
name change
Looks like option #2 is better.
Cheers
On Jul 6, 2013, at 1:22 AM, lars hofhansl wrote:
> So I cannot fix the maven release after the fact. So we have the following
> options:
>
> 1. Leave it as is. Tags/tar have HBASE-8656, but the maven release misses
> that that one fix; and release 0.94
I'll wait for some more comments.
In case of #2 I'd branch 0.94.9.1 from the 0.94.9 tag and just change pom.xml
to have the new name, and build new tars. No new vote on that release.
-- Lars
From: Ted Yu
To: "dev@hbase.apache.org"
Cc: "dev@hbase.apache.or
Chao Shi created HBASE-8884:
---
Summary: Pluggable RpcScheduler
Key: HBASE-8884
URL: https://issues.apache.org/jira/browse/HBASE-8884
Project: HBase
Issue Type: Improvement
Components: IPC/
Jimmy Xiang created HBASE-8885:
--
Summary: Fix and reenable TestGet failing#testDynamicFilter
Key: HBASE-8885
URL: https://issues.apache.org/jira/browse/HBASE-8885
Project: HBase
Issue Type: Test
I am still leaning towards #1. There is no bug, just one jira missing from the
maven release for two weeks or so (until 0.94.10 is released).
HBASE-8656 has no functional implications but fixes a condition where sometimes
handler threads are leaked with secure HBase only.
Furthermore this issue
An interesting question is how something like this can be avoided in the
future. The problem here was that tarball and the tag are created in separate
steps and that the tarball is build from the branch (not from the release SVN
tag).
What we could do is setup a tempory jenkins build for the sp
On Saturday, July 6, 2013, lars hofhansl wrote:
> What we could do is setup a tempory jenkins build for the specific release
> tag and use that to build the release.
> The advantage is that that build - including the test run, etc - is there
> for everybody to see. The tag-jenkins build can be del
Are these times or ops/sec, or something else?
- Original Message -
From: Jean-Marc Spaggiari
To: dev@hbase.apache.org; lars hofhansl
Cc:
Sent: Friday, July 5, 2013 8:24 PM
Subject: Re: [ANNOUNCE] The 1st hbase 0.94.9 release candidate is available
for download
I have redo the test
For option #1, some users would obtain 0.94.9 from download site yet others
would obtain from maven repo.
This means that there would be inconsistency among 0.94.9 users down the
road.
Is this desirable ?
On Sat, Jul 6, 2013 at 9:09 AM, lars hofhansl wrote:
> I am still leaning towards #1. Ther
Ted Yu created HBASE-8886:
-
Summary: Document FuzzyRowFilter in Ref Guide
Key: HBASE-8886
URL: https://issues.apache.org/jira/browse/HBASE-8886
Project: HBase
Issue Type: Bug
Reporter: Te
Hi Lars,
It's rows/seconds for 1M rows (1M writes, the 1M RandomReads, only
measuring the reads).
I have the same test with 2M running for all 0.94 the releases to see
if it makes a difference.
JM
2013/7/6 lars hofhansl :
> Are these times or ops/sec, or something else?
>
>
>
>
> - Original
In HBASE-8877 I'm proposing to change row locks to be reentrant and thread
based rather than tracking lock ids. Part of that change would mean
altering the RegionObserver coprocessor. Specifically, the methods
preBatchMutate and postBatchMutate would have the parameter
MiniBatchOperationInProgres
On Sat, Jul 6, 2013 at 2:49 PM, Dave Latham wrote:
> In HBASE-8877 I'm proposing to change row locks to be reentrant and thread
> based rather than tracking lock ids. Part of that change would mean
> altering the RegionObserver coprocessor. Specifically, the methods
> preBatchMutate and postBat
+1 on the removal of lock Ids.
On Sat, Jul 6, 2013 at 2:49 PM, Dave Latham wrote:
> In HBASE-8877 I'm proposing to change row locks to be reentrant and thread
> based rather than tracking lock ids. Part of that change would mean
> altering the RegionObserver coprocessor. Specifically, the meth
On Fri, Jul 5, 2013 at 5:21 PM, Varun Sharma wrote:
> I just set this value in hbase-site.xml but still the 7 byte reads and
> lseek(s) persist.
>
>
c. dfs.client.read.shortcircuit.skip.checksum is the key to bypass checksum
check at the client side. (from hdfs-2246 release notes).
It is red he
Ted Yu created HBASE-8887:
-
Summary: TestAdmin#testForceSplitMultiFamily fails intermittently
Key: HBASE-8887
URL: https://issues.apache.org/jira/browse/HBASE-8887
Project: HBase
Issue Type: Bug
stack created HBASE-:
Summary: Tweak retry settings some more, *some more*
Key: HBASE-
URL: https://issues.apache.org/jira/browse/HBASE-
Project: HBase
Issue Type: Bug
Reporte
Ted Yu created HBASE-8889:
-
Summary: TestIOFencing#testFencingAroundCompaction occasionally
fails
Key: HBASE-8889
URL: https://issues.apache.org/jira/browse/HBASE-8889
Project: HBase
Issue Type: Bug
+1 from me for changing the CP signature by removing lockids.. CP will be
able to acquire lock on rows? (lockRow will be still public?)
-Anoop-
On Sun, Jul 7, 2013 at 3:34 AM, Ted Yu wrote:
> +1 on the removal of lock Ids.
>
> On Sat, Jul 6, 2013 at 2:49 PM, Dave Latham wrote:
>
> > In HBASE
22 matches
Mail list logo
