This RC failed. It had a binding +1 and two -1s inside the voting allotment
but discussion says a new RC will get more attention.
S
On Wed, Apr 18, 2018 at 2:37 PM, Josh Elser wrote:
> I like that plan. I'll try to dig into what a "better" fix might be for
> the random ports
I like that plan. I'll try to dig into what a "better" fix might be for
the random ports stuff tonight.
On 4/18/18 5:35 PM, Stack wrote:
On Wed, Apr 18, 2018 at 12:58 PM, Josh Elser wrote:
+1 (binding)
There are rough edges, of course, but I think this is more than
On Wed, Apr 18, 2018 at 12:58 PM, Josh Elser wrote:
> +1 (binding)
>
> There are rough edges, of course, but I think this is more than enough
> quality for a 2.0.0. Putting a line in the sand for 2.0 will help us
> continue to make changes that improve the product going
; >> This is intentional I think, check HBASE-20385.
> >>
> >> Regards,
> >> Ashish
> >>
> >> -Original Message-
> >> From: Umesh Agashe [mailto:uaga...@cloudera.com]
> >> Sent: Tuesday, April 17, 2018 4:01 AM
> >
+1 (binding)
There are rough edges, of course, but I think this is more than enough
quality for a 2.0.0. Putting a line in the sand for 2.0 will help us
continue to make changes that improve the product going forward with
more focus and get those changes into the hands of folks downstream.
uaga...@cloudera.com]
>> Sent: Tuesday, April 17, 2018 4:01 AM
>> To: dev@hbase.apache.org
>> Subject: Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is
>> available
>>
>> -1 non-binding (hbck with write operations disabled not included)
>>
>> down
>
> > > > This is intentional I think, check HBASE-20385.
> > > >
> > > > Regards,
> > > > Ashish
> > > >
> > > > -Original Message-
> > > > From: Umesh Agashe [mailto:uaga...@cloudera.com]
> > > >
> >
> > > bq. signatures & sums-
> > NOT
> > > OK
> > > (md5 checksums missing)
> > >
> > > This is intentional I think, check HBASE-20385.
> > >
> > > Regards,
> > > Ashish
>
>
> > Regards,
> > Ashish
> >
> > -Original Message-
> > From: Umesh Agashe [mailto:uaga...@cloudera.com]
> > Sent: Tuesday, April 17, 2018 4:01 AM
> > To: dev@hbase.apache.org
> > Subject: Re: [VOTE] First release candidate
iginal Message-
> From: Umesh Agashe [mailto:uaga...@cloudera.com]
> Sent: Tuesday, April 17, 2018 4:01 AM
> To: dev@hbase.apache.org
> Subject: Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is
> available
>
> -1 non-binding (hbck with write oper
dev@hbase.apache.org
Subject: Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available
-1 non-binding (hbck with write operations disabled not included)
download src & bin tar ball - OK
signatures & sums
-1 non-binding (hbck with write operations disabled not included)
download src & bin tar ball - OK
signatures & sums- NOT OK
(md5 checksums missing)
build from source (openjdk version "1.8.0_151") - OK
rat check
On Fri, Apr 13, 2018 at 10:53 AM, Josh Elser wrote:
> Was poking around with PE on a few nodes (I forget the exact
> circumstances, need to look back at this), and ran into a case where ~35
> regions were left as RIT
>
> 2018-04-12 22:05:24,431 ERROR
>
Was poking around with PE on a few nodes (I forget the exact
circumstances, need to look back at this), and ran into a case where ~35
regions were left as RIT
2018-04-12 22:05:24,431 ERROR
[master/ctr-e138-1518143905142-221855-01-02:16000]
procedure2.ProcedureExecutor: Corrupt pid=3580,
On Fri, Apr 13, 2018 at 8:07 AM, Peter Somogyi wrote:
> -1
>
> Tests under hbase-rsgroup fail in setup phase. It is related to
> HBASE-20224, some addendums were not backported to branch-2.0 which causes
> the failure. I'm reopening HBASE-20224 and backport 2 missing
On Fri, Apr 13, 2018 at 5:40 AM, Jean-Marc Spaggiari <
jean-m...@spaggiari.org> wrote:
> Do we have a list of tests that we know will not pass this release?
>
> I got those failures so far, but since I want to run multiple runs, I want
> to make sure to exclude the un-stable tests.
>
>
-1
Tests under hbase-rsgroup fail in setup phase. It is related to
HBASE-20224, some addendums were not backported to branch-2.0 which causes
the failure. I'm reopening HBASE-20224 and backport 2 missing commits.
On Fri, Apr 13, 2018 at 3:54 PM, Jean-Marc Spaggiari <
jean-m...@spaggiari.org>
Exactly what I was looking for! Thanks Sean!
2018-04-13 9:37 GMT-04:00 Sean Busbey :
> Hi JMS!
>
> Current flaky results for branch-2.0, generated today AFAICT:
>
> https://builds.apache.org/view/H-L/view/HBase/job/HBase-
>
Hi JMS!
Current flaky results for branch-2.0, generated today AFAICT:
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests-branch2.0/lastSuccessfulBuild/artifact/
you can look at the "dashboard.html" artifact for a human usable idea
of what we think is broken.
you can fetch
Do we have a list of tests that we know will not pass this release?
I got those failures so far, but since I want to run multiple runs, I want
to make sure to exclude the un-stable tests.
TestAssignmentManagerMetrics.testRITAssignmentManagerMetrics:152 Metrics
Should be equal expected:<1> but
bq. I'd imagine that if the difference were large, then yes, it should
be a blocker
-- or we as a community can decide to work on it in a follow-on release
making perf a priority (say, 2.1.0).
I see, thanks for the clarification boss, makes sense.
Best Regards,
Yu
On 13 April 2018 at 06:02,
On Thu, Apr 12, 2018 at 1:47 PM, Stack wrote:
> On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey wrote:
>
>> no compat report in the RC directory. does that mean we won't have one
>> in the dist area?
>>
>>
>> not a blocker; we've been inconsistent on it in
On Tue, Apr 10, 2018 at 8:58 PM, Yu Li wrote:
> HBASE-20188 is comparing latest 2.0 to our stable pointer 1.2.7, and there
> seems to be no conclusion yet, JFYI. While yes I believe more numbers could
> give us a broader view :-)
>
>
Yeah, what Yu Li says above. As is, hbase2
On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey wrote:
> no compat report in the RC directory. does that mean we won't have one
> in the dist area?
>
>
> not a blocker; we've been inconsistent on it in prior releases, but
> the trend seemed to be towards including it.
>
>
HBASE-20188 is comparing latest 2.0 to our stable pointer 1.2.7, and there
seems to be no conclusion yet, JFYI. While yes I believe more numbers could
give us a broader view :-)
And I'm not sure but is performance regression some kind of a blocker for
the release? Thanks.
Best Regards,
Yu
On 11
Do we have a ITBLL result and also some performance numbers? I could help
getting some performance numbers comparing to the version we use...
2018-04-11 5:50 GMT+08:00 Sean Busbey :
> no compat report in the RC directory. does that mean we won't have one
> in the dist area?
>
no compat report in the RC directory. does that mean we won't have one
in the dist area?
not a blocker; we've been inconsistent on it in prior releases, but
the trend seemed to be towards including it.
On Tue, Apr 10, 2018 at 3:47 PM, Stack wrote:
> The first release
The first release candidate for Apache HBase 2.0.0 is available for
downloading and testing.
Artifacts are available here:
https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
Maven artifacts are available in the staging repository at:
28 matches
Mail list logo