Release Frequency Experiments

As you may or may not have noticed, for 0.94 I'm playing with a "rapid release train" scheme. The train stops by every few weeks, when a jira is done it'll board the train and be part of the release, otherwise it simply waits for the next one. There's a little bit flexibility for important featu

Jenkins build is back to normal : HBase-0.94 #443

See

Re: Issue close rate exceeds the rate at which issues are opened!

And we're not even done with the house cleaning, yet. :) From: Stack To: HBase Dev List Sent: Thursday, August 30, 2012 9:19 PM Subject: Re: Issue close rate exceeds the rate at which issues are opened! On Thu, Aug 30, 2012 at 2:19 PM, Stack wrote: > See g

Re: Issue close rate exceeds the rate at which issues are opened!

On Thu, Aug 30, 2012 at 2:19 PM, Stack wrote: > See graph here: https://issues.apache.org/jira/browse/HBASE > > I don't think this has happened before in the history of the project. > I would have to write a fancy report to prove it but as far back as I > remember, we made issues at a rate far in

Build failed in Jenkins: HBase-TRUNK-on-Hadoop-2.0.0 #155

See Changes: [larsh] HBASE-6165 Replication can overrun .META. scans on cluster re-start (Himanshu Vashishtha) [larsh] HBASE-6550 Refactoring ReplicationSink to make it more responsive of cluster health (Himanshu Vashishth

答复: About slf4j usage

np, i am glad to do :) 发件人: saint@gmail.com [saint@gmail.com] 代表 Stack [st...@duboce.net] 发送时间: 2012年8月31日 6:47 到: dev@hbase.apache.org 主题: Re: About slf4j usage On Thu, Aug 30, 2012 at 12:49 AM, 谢良 wrote: > Hi, > > Seems we use an suboptimal loggi

Jenkins build is back to normal : HBase-0.92-security #128

See

Re: About slf4j usage

On Thu, Aug 30, 2012 at 12:49 AM, 谢良 wrote: > Hi, > > Seems we use an suboptimal logging pattern currently, it's better to use > parameterized feature per slf4j manual: > http://www.slf4j.org/faq.html#logging_performance. > Want to try making a patch? Thanks, St.Ack

Re: HBase Developer's Pow-wow.

On Thu, Aug 30, 2012 at 3:36 PM, Devaraj Das wrote: > Should we move it to that week to accommodate Lars? > We could. We had it set for the week of 10th so Andrew could come. Andrew could you come the following week? St.Ack

Re: HBase Developer's Pow-wow.

Should we move it to that week to accommodate Lars? On Aug 30, 2012, at 3:04 PM, Lars George wrote: > Bummer, I will be in PA the week after, i.e. 9/17. It would have been great > to see you all again. > > Lars > > On Aug 29, 2012, at 10:15 PM, Andrew Purtell wrote: > >> +1 >> >> I can be u

Re: [Discuss] Release 0.92.2?

+1 on limiting changes into 0.92. Just wanted to point out a patch that we may be able to pull part of to fix the test. - Dave On Thu, Aug 30, 2012 at 2:07 PM, Ted Yu wrote: > Looking at 5992.v11.patch, it is quite big, touching master, > AssignmentManager, etc. > > At this moment, I want to l

Re: HBase Developer's Pow-wow.

Bummer, I will be in PA the week after, i.e. 9/17. It would have been great to see you all again. Lars On Aug 29, 2012, at 10:15 PM, Andrew Purtell wrote: > +1 > > I can be up week of the 10th if that's convenient. > >- Andy > > On Wednesday, August 29, 2012, Jimmy Xiang wrote: > >> +1

Build failed in Jenkins: HBase-0.92-security #127

See -- [...truncated 7174 lines...] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.069 sec Forking command line: /bin/sh -c cd /x1/jenkins/jenkins-slave/workspace/HBase-0.92-securit

Re: [Discuss] Release 0.92.2?

5992.v11.patch couldn't be cleanly applied to 0.92 I got: ./src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java.rej ./src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java.rej ./src/main/java/org/apache/hadoop/hbase/master/HMaster.java.rej ./src/main/java/

Issue close rate exceeds the rate at which issues are opened!

See graph here: https://issues.apache.org/jira/browse/HBASE I don't think this has happened before in the history of the project. I would have to write a fancy report to prove it but as far back as I remember, we made issues at a rate far in excess of the rate at which we closed issues (Thanks to

Re: [Discuss] Release 0.92.2?

Well, if I remember well the test was flaky because of multiple bugs on draining servers management... (cf. the mail on test speed :-) ) On Thu, Aug 30, 2012 at 11:07 PM, Ted Yu wrote: > Looking at 5992.v11.patch, it is quite big, touching master, > AssignmentManager, etc. > > At this moment, I

Re: fastest way to run tests

Hi Jimmy, On Thu, Aug 30, 2012 at 8:50 PM, Jimmy Xiang wrote: > Is this a test case issue, or an issue with surefire? > There are issues with surefire, but in this case it's 90% us. Some of those red jenkins builds are because some tests are killed > as findHangingTest.sh shows them hanging.

Re: [Discuss] Release 0.92.2?

Looking at 5992.v11.patch, it is quite big, touching master, AssignmentManager, etc. At this moment, I want to limit the scope of changes going into 0.92 branch. Cheers On Thu, Aug 30, 2012 at 1:55 PM, Dave Wang wrote: > Does HBASE-5992 fix this? That fix is only in trunk right now. > > - Dav

Re: [Discuss] Release 0.92.2?

Does HBASE-5992 fix this? That fix is only in trunk right now. - Dave On Thu, Aug 30, 2012 at 1:52 PM, Ted Yu wrote: > Looking at TestDrainingServer failure: > > admin.enableTable(TABLENAME); > // Assert that every regionserver has some regions on it. > MiniHBaseCluster cluster = T

Re: [Discuss] Release 0.92.2?

Looking at TestDrainingServer failure: admin.enableTable(TABLENAME); // Assert that every regionserver has some regions on it. MiniHBaseCluster cluster = TEST_UTIL.getMiniHBaseCluster(); for (int i = 0; i < cluster.getRegionServerThreads().size(); i++) { HRegionServer hrs = c

Re: fastest way to run tests

This is very helpful, thanks! I played with it some time these days. The testing is much faster, which is great. However, there is one issue. With parallel testing, very likely, some tests will be killed. As a result, the build could 1 either fail, 2 or succeed with a smaller total num

Jenkins build is back to normal : HBase-0.92 #548

See

Re: HBase Developer's Pow-wow.

For 'Strategies for keeping Jenkins blue', we can take this opportunity to fix a few known flaky tests. Cheers On Wed, Aug 29, 2012 at 11:30 AM, Jonathan Hsieh wrote: > There are a couple discussions brewing and major changes being it would be > good to have a face-to-face pow-wow to demo, to d

Re: [paper]Solving Big Data Challenges for Enterprise Application Performance Management

On Thu, Aug 30, 2012 at 8:57 AM, Andrew Purtell wrote: > Did I assist? No. Maybe you mean attend? Likewise, no. *grin* yeah that was a french-ism, I meant attend. > > This certainly wasn't advertised per the HN headline, and must have been in > some other track than what I attended, because this

Build failed in Jenkins: HBase-0.92 #547

See -- [...truncated 1806 lines...] Running org.apache.hadoop.hbase.regionserver.TestQueryMatcher Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.462 sec Running org.apache.hadoop.hbase.region

Re: [paper]Solving Big Data Challenges for Enterprise Application Performance Management

Did I assist? No. Maybe you mean attend? Likewise, no. This certainly wasn't advertised per the HN headline, and must have been in some other track than what I attended, because this is the first I've heard of it. The conference is just over now otherwise I'd track down the authors. I attended th

[paper]Solving Big Data Challenges for Enterprise Application Performance Management

Please refer to: http://vldb.org/pvldb/vol5/p1724_tilmannrabl_vldb2012.pdf Which is also referred to on HN as "Benchmarks of Cassandra, HBase, VoltDB, MySql, Voldemort and Redis" Andrew P., I think you were at VLDB this year? Did you assist that presentation? J-D

Build failed in Jenkins: HBase-0.92 #546

See -- [...truncated 1810 lines...] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.124 sec Running org.apache.hadoop.hbase.util.TestCompressionTest Tests run: 1, Failures: 0, Errors: 0, Skip

Build failed in Jenkins: HBase-0.92-security #126

See -- [...truncated 7177 lines...] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.74 sec Forking command line: /bin/sh -c cd /x1/jenkins/jenkins-slave/workspace/HBase-0.92-security

Re: Refactoring checkAndPut and checkAndDelete to use doMiniBatchMutation

+1 Jon's suggestion. On Thu, Aug 30, 2012 at 3:52 PM, Jonathan Hsieh wrote: > Ram, > > +1 > > It would be great if the refactor made adding a "checkAndMututate" method > trivial to add. This method would do an atomic check and set that and if > successful allowed for atomic deletions and puts

Re: Refactoring checkAndPut and checkAndDelete to use doMiniBatchMutation

Ram, +1 It would be great if the refactor made adding a "checkAndMututate" method trivial to add. This method would do an atomic check and set that and if successful allowed for atomic deletions and puts on the same row. (current api only allow checkAndDelete, checkAndPut, and batchMutate). J

Re: Refactoring checkAndPut and checkAndDelete to use doMiniBatchMutation

Please go ahead. On Aug 30, 2012, at 2:53 AM, "Ramkrishna.S.Vasudevan" wrote: > Hi > > > > Currently the checkAndPut and checkAndDelete api internally calls the > internalPut and internalDelete. May be we can just call doMiniBatchMutation > only. This will help in future like if we have

Build failed in Jenkins: HBase-0.92-security #125

See Changes: [stack] HBASE-662 [shell] Cannot describe '.META.' or '-ROOT-' tables -- [...truncated 7194 lines...] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.988 sec For

Refactoring checkAndPut and checkAndDelete to use doMiniBatchMutation

Hi Currently the checkAndPut and checkAndDelete api internally calls the internalPut and internalDelete. May be we can just call doMiniBatchMutation only. This will help in future like if we have some hooks and the CP handles certain cases in the doMiniBatchMutation the same can be done while

Build failed in Jenkins: HBase-0.92 #545

See Changes: [stack] HBASE-662 [shell] Cannot describe '.META.' or '-ROOT-' tables [jmhsieh] HBASE-6686 HFile Quarantine fails with missing dirs in hadoop 2.0 -- [...truncated 1820 lines...] Tests run

Build failed in Jenkins: HBase-TRUNK-on-Hadoop-2.0.0 #154

See Changes: [nkeywal] HBASE-6683 Wrong warning in logs WARN org.apache.hadoop.ipc.HBaseServer: Methods length : 5 (Devaraj Das) [stack] HBASE-6524 Hooks for hbase tracing; REAPPLICATION [stack] HBASE-6524 Hooks for hbase

Re: HBase Developer's Pow-wow.

Hi, I won't attend it, but would it be possible to share the agenda on an editable support (google doc or alike)? I could then add some comments on the points you will be working on... Thanks in advance, Nicolas On Thu, Aug 30, 2012 at 9:05 AM, Ramkrishna.S.Vasudevan < ramkrishna.vasude...@huaw

RE: HBase Developer's Pow-wow.

Hi Latest improvement, Tuesday should be best for me. +1 for Tuesday. Regards Ram > -Original Message- > From: Devaraj Das [mailto:d...@hortonworks.com] > Sent: Thursday, August 30, 2012 11:42 AM > To: dev@hbase.apache.org > Subject: Re: HBase Developer's Pow-wow. > > Sure, Jon (assumi