Re: [VOTE] The 1st HBase 0.98.12.1 patch release candidate (RC0) is available, vote closing 5/20/2015

+1 Verified sums and sigs Built from source against hadoop versions 2.2.0, 2.3.0, 2.4.0, 2.4.1, 2.5.0, 2.5.1, 2.5.2 (went overboard, new to this :)) checked rat -- Regards, Appy

Re: Better code quality with more checkstyles

mentally fix these as we touch code or do you plan > some mass check style cleanup? > > I've recently started contributing again and like how the checkstyle > scripting enforces a monotonicly decreasing # of violations. > > On Monday, November 9, 2015, Apekshit Sharma <a...@clo

Better code quality with more checkstyles

Sometimes, looking at certain things in our code makes me think, 'How did it get in, there should be some kind of check for it!'. Looked at different checkstyles rules and I think we can enable the following ones to improve the formatting quality of our codebase. ImportOrder

Re: Better code quality with more checkstyles

Emm...do no replies mean "don't care" which means silent yes? :-) On Tue, Nov 10, 2015 at 3:11 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Last sunday, when i was bored, i thought 'let's fix some naive stuff, > oh.. checkstyles!'. After some time and few change

Re: Better code quality with more checkstyles

The cleanup needs to happen in > tandem with compile-time enforcement of the rules so that we don't let the > bit-rott set back in again. > > So really, it's about coordinating the roll-out with minimal impact on > active development. Proposals? > > On Tue, Nov 17, 2015 at 11:5

Cleanup admin.rb. Shell in general.

(Planning to do this tomorrow as part of our weekly code fixit. Will appreciate quick feedback.) Admin.rb either is a potpourri of functions or it's doing something I don't know yet. Will it make sense to move the function definitions to appropriate "shell/commands/.rb" files? Anything else

Re: Better code quality with more checkstyles

gt; > reasonable to me. > > > St.Ack > > > > > >> On Tue, Nov 17, 2015 at 4:54 PM, Apekshit Sharma <a...@cloudera.com> > > wrote: > > >> > > >> I agree. Sorry if I my message was lost in the boring sunday story, > but &

Checkstyle News

Hey, Checkstyles have changed recently. And while they are small changes, they do affect the codebase in big way as time progresses. New checkstyles were added in HBASE-14829. Description of the jira lists the new checks that were added. As of result of these new checks, our checkstyle error

Re: Consesus on removing a public method from IA.Private class whose instance is returned from IA.public class.

rticulars. I suggest filing a JIRA. > > > On Dec 2, 2015, at 4:36 PM, Stack <st...@duboce.net> wrote: > > > > Appy makes a pretty good argument. > > > > What in particular are we discussing Ashish? > > > > Thanks, > > St.Ack > > >

Re: -1 overall but +1 in individual tests

> > Cheers > > On Wed, Dec 2, 2015 at 7:48 PM, Apekshit Sharma <a...@cloudera.com> wrote: > > > I was staring at test-patch.sh for 15 minutes, but couldn't figure out > what > > could have been the error. Made sure that if any function was returning > 1, > &

Re: -1 overall but +1 in individual tests

Sorry, this is the one. https://issues.apache.org/jira/browse/HBASE-14917 On Wed, Dec 2, 2015 at 9:21 PM, Apekshit Sharma <a...@cloudera.com> wrote: > https://issues.apache.org/jira/browse/HBASE-14916 > > On Wed, Dec 2, 2015 at 7:52 PM, Ted Yu <yuzhih...@gmail.com> wrote

Re: -1 overall but +1 in individual tests

d 1 for anti pattern check, 2 for BuildWithHadoopVersions, 4 > for JavacWarnings, etc > > Cheers > > On Wed, Dec 2, 2015 at 7:18 PM, Apekshit Sharma <a...@cloudera.com> wrote: > > > Hi > > Any ideas what can be the re

-1 overall but +1 in individual tests

Hi Any ideas what can be the reason here? https://issues.apache.org/jira/browse/HBASE-14865?focusedCommentId=15037056=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15037056 -- Appy

Re: Consesus on removing a public method from IA.Private class whose instance is returned from IA.public class.

=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15032734 On Wed, Dec 2, 2015 at 5:32 PM, Andrew Purtell <andrew.purt...@gmail.com> wrote: > Ok, so no annotation change then. I looked at HBASE-14769. Change there > seems fine. > > > > On Dec 2, 2015, at 5:03 PM, Apekshit Sharma &

Re: Consesus on removing a public method from IA.Private class whose instance is returned from IA.public class.

; InterfaceAudience.Private). > > > > Now the question is, can we remove the public APIs from class 'A' without > > marking them deprecated ? > > > > I think we should not remove it directly, it will break the users using > > these(removed) public methods from cl

Re: truncated checkstyle output

ld/hbase/hbase-client/src/main/java/org/apache/hadoop/hbase/security/access/Permission.java"> > > Has anyone else noticed similar issue ? > > Thanks > -- Regards Apekshit Sharma | Software Engineer, Cloudera | Palo Alto, California | 650-963-6311

Re: [ANNOUNCE] New HBase committer Apekshit Sharma

; > >> > Congrats and welcome Appy! > > >> > > > >> > On Fri, Jun 3, 2016 at 10:58 AM Ted Yu <yuzhih...@gmail.com> wrote: > > >> > > > >> > > Congratulations, Appy. > > >> > > > > >>

Single command line to create patch, upload it to jira, and update review board

Hi folks Ref: https://issues.apache.org/jira/browse/HBASE-15892 The script does the following: - makes the patch (next version is determined by existing attachments in the jira) - Updates the review on RB. If review doesn't already exists, creates a new one and adds the link to the jira -

Re: Smart Flaky Handler

e, you're welcome (and encouraged) to borrow/steal it. If you make some > improvements, please let us know, though, so we can merge them back to our > copy > > The code for the server is here: > > https://github.com/apache/incubator-kudu/blob/master/build-support/test_result_server.py &

Re: Smart Flaky Handler

Okay, so it was because mvn install -Dtest=foo always runs the integration tests in addition to test foo. Whereas if I do mvn test -Dtest=foo, it only runs the test foo. This seems bug to me. Or is it by choice? If latter, what's the rationale? On Mon, May 30, 2016 at 2:37 AM, Apekshit Sharma

Re: Smart Flaky Handler

, Apekshit Sharma <a...@cloudera.com> wrote: > I see, thanks for explaining it to me Dima. > > On Mon, May 30, 2016 at 10:18 AM, Dima Spivak <dspi...@cloudera.com> > wrote: > >> Running the install phase of the lifecycle will run integration tests >> (since that p

Re: Single command line to create patch, upload it to jira, and update review board

Run this first : pip install gitpython && pip install rbtools On Thu, May 26, 2016 at 7:51 AM, Apekshit Sharma <a...@cloudera.com> wrote: > Hi folks > > Ref: https://issues.apache.org/jira/browse/HBASE-15892 > > The script does the following: > - makes the p

Re: Smart Flaky Handler

event that from happening. > > -Dima > > On Monday, May 30, 2016, Apekshit Sharma <a...@cloudera.com> wrote: > > > Okay, so it was because mvn install -Dtest=foo always runs the > integration > > tests in addition to test foo. > > Whereas if I do mvn test

Re: Hangout on Slack?

Or you can join the team using this link: https://apache-hbase.slack.com/shared_invite/NTIxMTE4NTQwMzYtMTQ2NjIwOTMwMi1kMzc2YzkwYTJm It expires on Sunday. On Fri, Jun 17, 2016 at 4:43 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Created slack team apache-hbase.slack.com. > It has

Re: Hangout on Slack?

at 3:20 PM, Dima Spivak <dspi...@cloudera.com> wrote: > +1. Even with all the bots, I feel really lonely in the #hbase IRC. :) > > -Dima > > On Thu, Jun 16, 2016 at 3:15 PM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > Brining it up again, because I re

Re: Hangout on Slack?

Anyone can join anytime with @apache.org email id using following link. https://apache-hbase.slack.com/x-37639653748-52658243986/signup Sorry, but slack doesn't allow doing same for @gmail.com email ids. On Mon, Jun 20, 2016 at 11:36 AM, Apekshit Sharma <a...@cloudera.com> wrote: > H

Re: Hangout on Slack?

py, could you make another link? if there's a "no-expiration" option > that would be best. > > On Fri, Jun 17, 2016 at 7:23 PM, Apekshit Sharma <a...@cloudera.com> > wrote: > > Or you can join the team using this link: > &g

Re: Surge of flaky tests

(Assert.java:834) > > > at org.junit.Assert.assertEquals(Assert.java:645) > > > at > > > > > > > > > org.apache.hadoop.hbase.client.TestFastFail.testCallQueueTooBigException(TestFastFail.java:327) > > > > > > > > > Results : > > > >

Re: Task #57953b5d

Hi Rohit Welcome to HBase community. We can certainly help you get started/learn more about HBase depending on your current familiarity. HBase book [1] is going to be immensely helpful resource. I suggest you start with 'Data Model' and 'Building and

Re: Flaky tests

t; Ram > > On Fri, Jun 24, 2016 at 9:09 AM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > Oh, this missed my view. > > Yeah, these flaky tests are big pain. At the very least, we should file > the > > jiras for them. I don't think everyone tracks the builds or

Re: Flaky tests

Oh, this missed my view. Yeah, these flaky tests are big pain. At the very least, we should file the jiras for them. I don't think everyone tracks the builds or the dashboard (yet), but many do track the jiras. Instead of RMs cracking down on them on every minor/major release, maybe everyone in

Surge of flaky tests

Hi I am seeing a sudden surge in number of flaky tests. http://hbase.x10host.com/flaky-tests/ I'd request everyone to have a look at the list and see if any test failure correlates with recent changes you made. To go to failing runs, click on show/hide next to that test. -- Appy

Re: Trying to understand checkstyle with Yetus

> > -- the difference between the branch and patch versions of the checkstyle > > output is calculated[2] and stored in diff-checkstyle-${module}.txt > > > > > > > > Sounds like we (Yetus) should build some overview docs on plugins. Thanks > > for the

Trying to understand checkstyle with Yetus

So looking at artifacts of a build ( https://builds.apache.org/job/PreCommit-HBASE-Build/261/artifact/patchprocess/), I see checkstyle for only 'hbase-server', why so? Is it that we haven't turned it on for other modules yet? Also I see following five different files, what is each one for? -

Re: [VOTE] HBase 1.2.0 RC3

] +1 Release this package as Apache HBase 1.2.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... > > > > Vote will be subject to Majority Approval[2] and will close at 6:00PM UTC > > on Wednesday, Feb 17th, 2016[3]. > > > > [1]: http://www.apache.org/info/verification.html > > [2]: https://www.apache.org/foundation/glossary.html#MajorityApproval > > [3]: to find this in your local timezone see: > > http://s.apache.org/hbase-1.2.0-rc3-close > > > -- Regards Apekshit Sharma | Software Engineer, Cloudera | Palo Alto, California | 650-963-6311

Re: Better management of flakies

So tackling the two parts individually: 1) Detection : A good automatic flaky detector will no doubt save manual effort. The one mentioned by Matteo seems like a good one which we can hook up with post-commit job. I see a minor problem though, we'll should use about 20 runs at least, but the rate

Re: Better management of flakies

So who's setting up the jobs? I don't have perms to do it. On Wed, Mar 30, 2016 at 11:24 AM, Apekshit Sharma <a...@cloudera.com> wrote: > So tackling the two parts individually: > 1) Detection : A good automatic flaky detector will no doubt save manual > effort. The one mentioned

Better management of flakies

Proposal: Maintain a list of flaky tests which can be ignored in main builds (for patches) and setup a new job which will periodically run those flaky tests. Benefits: - Cleaner main builds. Less runs per patch, ideally no re-runs because of timeouts and other flakiness. Less frustration.

Re: Better management of flakies

ripts > > in dev-support so that the commiter-only change can just be moving > > jenkins to execute them. > > > > > I like this idea Sean. > St.Ack > > > > > On Fri, Apr 1, 2016 at 12:01 PM, Apekshit Sharma <a...@cloudera.com> > > wrote: >

Hangout on Slack?

"Committers should hang out in the #hbase room on irc.freenode.net for real-time discussions." -- HBase Book The room has a bunch of people, but none who I recognize. I wonder what happened. How a room which I imagine must have had thriving geeky discussions once, just died. Anyways, let's

Re: API compatibility history for HBase

gt; Hi Folks! > > > > The developer behind the Java API Compatibility Checker tool has been > > working on tools to show API changes over time. He was gracious enough > > to add us to his list of examples: > > > > http://abi-laboratory.pro/java/tracker/timeline/

Re: Smart Flaky Handler

dureStore.java,**/TestRegionMergeTransactionOnCluster.java,**/TestSaslFanOutOneBlockAsyncDFSOutput.java,**/TestReplicationEndpointWithMultipleWAL.java, > > > > > > Whats the '**/' about? Is it supposed to have opening/closing versions? > > > > > > Thanks bos

Re: Smart Flaky Handler

s themselves. > > -Todd > -- > Todd Lipcon > Software Engineer, Cloudera > -- Regards Apekshit Sharma | Software Engineer, Cloudera | Palo Alto, California | 650-963-6311

Need reviews on shell code

These are two cleanups i did on shell code. Need reviews. https://reviews.apache.org/r/47476/ https://reviews.apache.org/r/47493/ Next to come are patches for 1. Simple Command parser, which will do the following: - bettter error reporting - better help messages - easier command parsing 2.

Smart Flaky Handler

This mail is to introduce the work to tackle the flaky tests in our build. *Why is it important?* - Our build history sucks, last 175 post-commit runs failed. We need to make it useful. - To better understand our code’s testing status, more importantly it’s weak points. - We know those 2-3 tests

Re: Hangout on Slack?

mudgeonly. Sure, > why not? If that's where people want to gather. You creating a room? How to > make it "official"? > > On Mon, Apr 25, 2016 at 4:22 PM, Stack <st...@duboce.net> wrote: > > > On Mon, Apr 25, 2016 at 4:05 PM, Apekshit Sharma <a...@cloudera.com&

Re: Hangout on Slack?

here's the question of searchable archives. Are IRC/Slack channels > > archived so users 3 months later can find the answer that someone else > > posted? Again, Apache has policies that dictate this as well. > > > > I'm not saying don't do it. I'm asking what your objective is.

Re: Reminder: Please use git am when committing patches

ionally, as a PMC member it is much easier to try > to build an idea of contributions to the repo over time if I can scan > through git author and sign-off tags than if I have to try to pick out > bespoke commit message details. > > > > On Thu, Jan 26, 2017 at 8:45 PM, Apekshit Shar

Re: Git Pull Request to HBase

Thu, Jan 26, 2017 at 11:47 AM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > Hi Chetan, Ted > > > > It's the right question to ask. One who does the work should get the > > credits, and that means commit authorship too. > > That's where the script subm

Re: Git Pull Request to HBase

Hi Chetan, Ted It's the right question to ask. One who does the work should get the credits, and that means commit authorship too. That's where the script submit_patch.py which i wrote a while back helps too. If contributors use the script to submit formatted patch (instead of just git diff and

Reminder: Please use git am when committing patches

Hi devs, A recent question by new contributor (thread: Git Pull Request to HBase) and looking at history of commits, i think it is worth re-iterating that committer should use *git am* while committing patches so that whoever did the actual work gets appropriate credit in git history. In case the

Re: Reminder: Please use git am when committing patches

. One more thing is that, do > not > > > forget to add --signoff :) > > > > > > Mind opening a issue to modify the above section in hbase book, Appy? > > > > > > Thanks. > > > > > > 2017-01-27 4:12 GMT+08:00 Che

Re: Merge and HMerge

>>>> > > >>>> We should not have any tool which will work in offline mode by going > > >> over > > >>>> the HDFS data. Seems very brittle to be broken when things get > > changed. > > >>>> Only use ca

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

@Sean, Mikhail: I found the alternate solution. Using user defined axis, tool environment and env variable injection. See latest diff to https://builds.apache.org/job/HBase-Trunk_matrix/ job for reference. On Tue, Aug 30, 2016 at 7:39 PM, Mikhail Antonov wrote: > FYI, I

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

://builds.apache.org/view/H-L/view/HBase/job/HBASE-Flaky-Tests/) which was disabled for almost a month due to trunk being on fire. I will keep an eye on how things are going. On Mon, Sep 12, 2016 at 2:02 PM, Apekshit Sharma <a...@cloudera.com> wrote: > @Sean, Mikhail: I found the alternate soluti

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

Emm, can it be because scalatest tries to use a different java then that specified by JAVA_HOME (which is used to compile) On Thu, Sep 15, 2016 at 2:10 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Andeverything is back to red. > Because something is plaguing our

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

eased or otherwise > supposedly stable branches. > > -Mikhail > > On Mon, Sep 12, 2016 at 4:53 PM, Sean Busbey <bus...@cloudera.com> wrote: > > > awesome work Appy! > > > > That's certainly good news to hear. > > > > On Mon, Sep 12, 2016 at 2:14 PM,

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

jdk8 or > needs to be updated to a jdk8 compatible version. > > > -- > *With Regards:-* > *Aman Poonia* > > On Fri, Sep 16, 2016 at 2:40 AM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > Andeverything is back to red. > > Because something is plagu

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

w, right? Also, it looks like the hbase-spark > > integration-test phase is what's tripping up the build. Why not just > > temporarily disable that to unblock testing? > > > > On Friday, September 16, 2016, Apekshit Sharma <a...@cloudera.com> > wrote: > > > >

Re: [ANNOUNCE] Misty Stanley-Jones joins the Apache HBase PMC

Congrats Misty! On Wed, Sep 7, 2016 at 11:56 AM, Andrew Purtell wrote: > Congratulations, Misty! > > On Wed, Sep 7, 2016 at 11:40 AM, Sean Busbey wrote: > > > On behalf of the Apache HBase PMC I am pleased to announce that Misty has > > accepted our

Use hemcrest in hbase

Hey guys, Hemcrest seems like a wonderful library of matchers for unit testing. Am sure our tests can use that improvement. Any good reason it's not widely used in hbase? I'll start using it more often unless there's a good reason not to. It's BSD licence, that's compatible with Apache? -- Appy

Re: Update apache cli version from 1.2 to 1.3.1?

It's for 2.0. The work am planning to do, using apache cli in our tools, will be in master only to avoid compatibility issues. On Mon, Oct 31, 2016 at 8:37 PM, Sean Busbey <bus...@apache.org> wrote: > update for which version(s) of HBase? > > On Mon, Oct 31, 2016 at 6:31 PM,

Re: Merge and HMerge

bq. HMerge can merge multiple regions by going over the list of regions and checking their sizes. bq. But both of these tools (Merge and HMerge) are very dangerous I came across HMerge and it looks like dead code. Isn't referenced from anywhere except one test. (This is what lars also pointed out

Update apache cli version from 1.2 to 1.3.1?

1.3 came out in 2015, 6 years after 1.2. It was few bug fixes and new features. These are few good/important ones: - HelpFormatter now prints command-line options in the same order as they have been added. Fixes CLI-212. - Standard help text now shows mandatory arguments also for the first

Re: Hangout on Slack?

ther thread, do > you > > > have to have an apache.org id to join up? > > > > > > The Slack channel should be published on the website? Is it there (I > > don't > > > see it on a quick search on site and in refguide but I could be blind). > > >

Re: Hangout on Slack?

hread, do > you > > > have to have an apache.org id to join up? > > > > > > The Slack channel should be published on the website? Is it there (I > > don't > > > see it on a quick search on site and in refguide but I could be blind). > > > >

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

@stack, it compiled for me. Also tried few commands, and have to say, it's well designed from user commands perspective. On Tue, Oct 11, 2016 at 5:08 PM, Stack wrote: > On Tue, Oct 11, 2016 at 1:50 PM, Vladimir Rodionov > > wrote: > > > Michael, > >

Re: [DISCUSSION] Merge Backup / Restore - Branch HBASE-7912

t;>> >>> > apache/hadoop/hbase/io/encoding/rowindexV1/RowIndexCodecV1.j > > >>>> ava:[45,8] > > >>>> >>> > org.apache.hadoop.hbase.io.encoding.rowindexV1. > RowIndexCodecV1 > > is > > >>>> not > > >>&g

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

the other jobs. I don't see > > a downside. Anyone else have concerns? > > > > > > On Fri, Sep 16, 2016 at 6:15 PM, Apekshit Sharma <a...@cloudera.com> > > wrote: > > > So this all started with spaces-in-path issue, right? I think it has > > &g

Should we remove Mob Sweeper MR job

>From what i understand, it was part of initial implementation of MOB but was later replaced by DefaultMobStoreCompactor and ExpiredMobFileCleaner. Let's remove this 1500+ lines tool if it's redundant, because it's unnecessary maintainence. I stumbled across it when i was trying to replace zk

Re: [ANNOUNCE] New HBase committer Phil Yang

Congratulations Phil! On Tue, Nov 29, 2016 at 10:36 AM, Jerry He wrote: > Congratulations and welcome, Phil. > > On Tue, Nov 29, 2016 at 9:35 AM, Huaxiang Sun wrote: > > > Congratulations, Phil! > > > > > On Nov 29, 2016, at 5:29 AM, Yu Li

Re: [ANNOUNCE] New HBase committer Lijin Bin

Congratulations Lijin. On Tue, Nov 29, 2016 at 10:35 AM, Jerry He wrote: > *Congratulations, *宾莉金! > > On Tue, Nov 29, 2016 at 9:34 AM, Huaxiang Sun wrote: > > > > > Congratulations, Lijin! > > > > > On Nov 29, 2016, at 5:15 AM, 宾莉金 or binlijin

Re: ANNOUNCE: Good news!!!! Two new PMC and a new Committer!

Congrats Josh, Jing and Eshcar! On Sun, Mar 19, 2017 at 6:08 PM, 宾莉金 or binlijin wrote: > Congratulations and welcome! > > 2017-03-18 8:42 GMT+08:00 Yi Liang : > > > Congratulations, Jerry and Josh Elser > > > > Best, > > Yi > > > > On Fri, Mar 17,

Re: Slack access

Samir Ahmic <ahmic.sa...@gmail.com> > wrote: > > > Hi Dima, > > > > Mind sending me invite to channel to? > > Thanks chief. > > > > Best Regards > > Samir > > > > On Mon, Jul 24, 2017 at 8:28 AM, Apekshit Sharma <a...@cloudera.com> >

Re: Ycsb and Hbase - read+write simulation.

not clear on what's the ask here. Going by just two sentences, am confused how it can be 97% in last 2 hours but only 90% in 24 hours? Shouldn't second number be larger? -- Appy On Wed, Aug 9, 2017 at 1:01 AM, Meirav Malka wrote: > -- Forwarded message --

Re: [DISCUSS] hbase-2.0.0 compatibility expectations

Ref: deleting/deprecating some methods in HBaseAdmin https://github.com/apache/hbase/commit/de696cf6b653749c6bf105ef3d62d7a6c6923c57 >From first message: *" An hbase1 client can run against an hbase2 cluster but it will only be able to do DML (Get/Put/Scan, etc.). We do not allow being able to do

Re: Flaky Test Dashboard Empty

Looks like the latest build which you kicked off passed. It was on H22 too, so maybe no need to exclude? On Fri, Jul 7, 2017 at 3:49 PM, Mike Drob wrote: > Hi Folks, > > I was looking at the flaky test dashboard and noticed that the aggregation > job failed[1] > > It's been

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

Fixed 'trends' in flaky dashboard. Since i changed the test names in last fix, the dots in the name were messing up with CSS selectors. :) On Mon, Jul 10, 2017 at 11:34 AM, Apekshit Sharma <a...@cloudera.com> wrote: > Quick update on flaky dashboard: > Flaky dashboard wasn't wor

Re: Testing and CI -- Apache Jenkins Builds (WAS -> Re: Testing)

Quick update on flaky dashboard: Flaky dashboard wasn't working earlier because our trunk build was broken. After trunk was fixed, the format of log lines in consoleText was not the same, so findHangingTests.py was not able to parse it correctly for broken/hanging/timeout tests. That's been fixed

Re: Slack access

There are 2 other ways: - whitelist domain names. For eg. @apache.com. - Signup link which anyone can use to join the group. Sadly, that remains alive only for a day or two. On Sun, Jul 23, 2017 at 9:47 AM, Sachin Jain wrote: > As long as you are fine with sending

Re: org.apache.hadoop.hbase.snapshot.TestSecureExportSnapshot broken in branch-1?

So the issue here is, somehow Test*ExportSnapshot (4 tests classes) tests are stepping on each other. When we run locally, tests are run sequentially, hence they always pass. But in precommit/flaky-tests-job, there are multiple forks and multiple tests can run in parallel. That's when they fail.

Re: flaky test report

Retention policy for that job is max 7 day, max 20 builds. https://builds.apache.org/job/HBASE-Flaky-Tests/configure Tuned it up to 100 builds. On Fri, May 5, 2017 at 3:13 PM, Ted Yu wrote: > Hi, > I was looking at > https://builds.apache.org/job/HBASE-Find-Flaky-Tests/ >

Re: Please congratulate our new PMC Chair Misty Stanley-Jones

Congrats Misty! Wohooo! -- Appy On Thu, Sep 21, 2017 at 2:17 PM, Mike Drob wrote: > Rock on, Misty! > > On Thu, Sep 21, 2017 at 2:35 PM, Sean Busbey wrote: > > > congrats Misty! > > > > On Thu, Sep 21, 2017 at 2:08 PM, Andrew Purtell

Re: [DISCUSS] Coprocessor major design changes HBASE-17732

Just realized that earlier linked doc might not be accessible publicly. Here's the new link : https://docs.google.com/document/d/1mPkM1CRRvBMZL4dBQzrus8obyvNnHhR5it2yyhiFXTg/edit?usp=sharing -- Appy On Wed, Sep 6, 2017 at 5:07 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Hi > &g

[DISCUSS] Coprocessor major design changes HBASE-17732

Hi Links: HBASE-17732 , Code Review With 2.0 beta 1 approaching, this seems to be the ripe time to make much needed coprocessor design changes. Here's a summary of what's changing (from jira description):

Re: [DISCUSS] Merging Hybrid Logical Clocks with Master

It's true that hlc clock is very slower than system, but is it really a bottleneck? I mean 7mil ops/sec with 16 threads doesn't sound bottleneck because: - It's like 70 times of any RS' throughput (assuming 100k write throughput) - It's certainly enough for meta operations. What say? But i

Re: [DISCUSS] Merging Hybrid Logical Clocks with Master

demonstrate that perf is > not affected by HLC. > > Enis > > On Fri, Aug 25, 2017 at 2:00 PM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > It's true that hlc clock is very slower than system, but is it really a > > bottleneck? I mean 7mil ops/sec with 16 threa

Re: [DISCUSS] Fate of CoordinatedStateManager and hbase.coordinated.state.manager.class config

2017 at 1:15 PM, Andrew Purtell <apurt...@apache.org> > wrote: > > > Sounds good to me. > > > > > > On Mon, Oct 23, 2017 at 1:00 PM, Apekshit Sharma <a...@cloudera.com> > > wrote: > > > > > Thanks Andrew! > > > > >

Re: [DISCUSS] Fate of CoordinatedStateManager and hbase.coordinated.state.manager.class config

o need necessarily to abandon > the idea of abstraction between our coordination needs and the > implementation. > > > On Mon, Oct 23, 2017 at 12:16 PM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > Hi everyone, > > > > Am coming from limited kno

Re: [DISCUSS] Punt the Coprocessor TableWrapper and CoprocessorHConnection?

+1 I remember Andrew saying same thing about CoprocessorEnvironment#getTable functions during the review of HBASE-17732, that we should get rid of them and let CP do their own table resource management like all other things. On Wed, Oct 18, 2017 at 2:45 PM, Stack wrote: >

[DISCUSS] Fate of CoordinatedStateManager and hbase.coordinated.state.manager.class config

Hi everyone, Am coming from limited knowledge here, so pardon me if it seems outrageous. I guess this effort (HBASE-10909 ) was to separate out state into an interface which was then made pluggable via the config

Re: [DISCUSS] Any committers willing to do maintenance releases over the holidays?

compatibility > report. > >> > >> Who will carry this banner? Apekshit, Jan: shall we draw straws? One of > >> you > >> have a bit of extra free time over the next 4 weeks? > >> > >> Thanks, > >> Nick > >> > >> On Wed, N

Can we always add new regions as CLOSED?

Hi folks, Was debugging TestTruncateTableProcedure when starting thinking about this. (That's one mean test! What nice fault tolerant tests!) So the specific case: If we fail after adding new regions to meta ( TRUNCATE_TABLE_ADD_TO_META

Re: Moving To SLF4J and Log4J2

, but we need clear picture now. 4) Followup jira for hbase-backup/http or a reason why they can't be done. Reverting this patch would be hell, wouldn't want to do it because we missed basic checks. -- Appy On Mon, Dec 18, 2017 at 3:53 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Oh

Re: Moving To SLF4J and Log4J2

Oh, just 60 pages of review :D -- Appy On Mon, Dec 18, 2017 at 3:48 PM, Stack <st...@duboce.net> wrote: > On Wed, Dec 13, 2017 at 10:09 AM, Stack <st...@duboce.net> wrote: > > > On Mon, Dec 11, 2017 at 12:49 PM, Apekshit Sharma <a...@cloudera.com> > >

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

was planned and was decided not to be done. It's new. And new things can be important! On Wed, Nov 1, 2017 at 4:34 PM, Apekshit Sharma <a...@cloudera.com> wrote: > Came here just to track anything related to Distributed Log Replay which I > am trying to purge. But looks like it's anothe

Re: [DISCUSSION] Items to purge from branch-2 before we cut hbase-2.0.0-beta1.

Came here just to track anything related to Distributed Log Replay which I am trying to purge. But looks like it's another discussion thread about hbase-backup. Am coming here with limited knowledge about the feature (did a review initially once, lost track after). But then, looks like discussion

Re: Moving To SLF4J and Log4J2

Seems like good idea: - remove long dead dependency - a bit cleaner code - hadoop also moved to slf4j Quickly looking at codebase to get idea of amount of work required, here are some numbers: - LOG.debug : ~1800 - LOG.trace : ~500 - LOG.info: ~3000 Looking at this patch (

Re: Suggestion to speed up precommit - Reduce versions in Hadoop check

"| -1 |hadoopcheck" `ls 1*` | awk '{x[$1] = 1} END{for (i in x) print i;}' | wc -l Number of passed runs: grep "| +1 |hadoopcheck" `ls 1*` | awk '{x[$1] = 1} END{for (i in x) print i;}' | wc -l -- Appy On Mon, Dec 11, 2017 at 4:07 PM, Apekshit Sharma <a...@clo

Suggestion to speed up precommit - Reduce versions in Hadoop check

Hi +1 hadoopcheck 52m 1s Patch does not cause any errors with Hadoop 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 2.7.4 or 3.0.0-alpha4. Almost 1 hr to check against 10 versions. And it's only going to increase as more 2.6.x, 2.7.x and 3.0.x releases come out. Suggestion here is simple,

  1   2   >