hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yu Li <car...@gmail.com>
Subject Re: State of 1.3 first RC
Date Tue, 01 Nov 2016 17:03:25 GMT
Another critical one for your attention sir (patch ready for commit):
https://issues.apache.org/jira/browse/HBASE-16960

Best Regards,
Yu

On 31 October 2016 at 16:59, Mikhail Antonov <olorinbant@gmail.com> wrote:

> Hi Yu,
>
> sorry I missed that and thanks for reaching out. Let me have a look now and
> comment on the jira.
>
> -Mikhail
>
> On Mon, Oct 31, 2016 at 12:30 AM, Yu Li <carp84@gmail.com> wrote:
>
> > I think HBASE-16931 is also a critical issue (oops also in compaction
> > area...) and should go in 1.3.0, pinged several times there but failed to
> > draw your attention boss (smile). Mind take a look? Thanks.
> >
> > Btw, is there any ETA for 1.3.0 yet?
> >
> > Best Regards,
> > Yu
> >
> > On 29 October 2016 at 08:17, Mikhail Antonov <olorinbant@gmail.com>
> wrote:
> >
> > > Guys,
> > >
> > > I've been working on getting the first RC out this week and want to
> share
> > > an update on the current state of the things.
> > >
> > >  - HBASE-16951 - was found and fixed, when we don't include
> > > hbase-archetypes in the tarball assembly
> > >  - HBASE-16570 - optimization that caused a regression in the balancer,
> > it
> > > was reverted from 1.3. Once fixed that would go to 1.4 and perhaps
> 1.3.1.
> > >  - HBASE-16743 - flaky TestSimpleRpcScheduler, fixed now (I ran several
> > > cycles of 50 iterations each and all have passed).
> > >
> > > Now, there's presently one remaining blocker - HBASE-16964, when we
> don't
> > > properly handle archiving of store files after compactions (thanks Gary
> > for
> > > digging into that!).
> > > See the jira for details.
> > >
> > > Also, as a note - the above is a third major bug around compactions
> that
> > we
> > > saw on 1.3 during our testing last month (see also HBASE-16788
> > > and HBASE-16754)..
> > > So during the upcoming RC testing let's try to stress this area.
> > >
> > > Until 1.3 is out let's consider branch-1.3 to be in a lockdown for new
> > > changes. Ping me if you think there is something that I'm missing that
> > > should go out in 1.3. Otherwise,
> > > important but non-blocker fixes in flight would go in 1.3.1.
> > >
> > > Stay tuned!
> > > Mikhail
> > >
> >
>
>
>
> --
> Thanks,
> Michael Antonov
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message