hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Purtell <apurt...@apache.org>
Subject Re: [DISCUSSION] Finishing up 0.96 --> WAS Re: 0.95 and 0.96 remaining issues
Date Wed, 17 Jul 2013 20:45:11 GMT
> +Packaging

I would like to help you on this. Can do packaging and testing using the
Bigtop framework. I see HBASE-8187, but it's resolved. Elsewhere we
can coordinate? Could open a Bigtop jira. Whatever you prefer.

> +Migration

As part of the above. Test by starting with an 0.94 install on a small
cluster, load up some data, shut down and upgrade packages, try to
(re)launch...

> What else?

I beg your patience as RM. Some guys here have been working diligently for
the past couple of months on something that is in our estimation 0.96able.
Won't go into it here because they have been passing around a proposal for
dev@ since the weekend, to make sure it says what they want. Will be out in
the next day or so for the consideration of all.



On Wed, Jul 17, 2013 at 12:12 PM, Stack <stack@duboce.net> wrote:

> STATUS
>
> +Build
>
> A few of us have been working on broke junit tests.  Progress is slow but
> steady.  Currently I am looking into zombie tests -- "all" tests complete
> but the build still fails.  Andrew Purtell has set me up w/ a clone box
> from his ec2 rig which is helping figure the zombie phenomenon.  I also
> just added our hadoopqa zombie detector up on apache trunk build to see if
> it yields clues at nkeywals' suggestion.  I also need to fix
> https://issues.apache.org/jira/browse/HBASE-8764 so the ec2 integration
> test build passes (ec2 build runs integration tests which apache build does
> not)
>
> +Reviews
>
> Francis' namespaces is in need of review as are other 'Patch Available'
> criticals that we'd like committed such as Sergey's compaction changes.  If
> any volunteers are game, see the 'patch available' issues here [1].
>  Contrib appreciated.
>
> +Testing
> I know of at least one rig that is going up to do long-term hbase-it tests.
>  Any other testing going on that folks would like to talk up?
>
> +Migration
>
> Testing and finish documentation on moving from 0.94 pedigree to 0.96.
>  Still TODO.
>
> +Packaging
>
> Making it so we can publish an hbase 0.96 built against hadoop1 and
> hadoop2.  Still TODO.
>
> What else?
>
> I am still heading for end of July for a complete '0.96'.
>
> Thanks,
> St.Ack
>
> 1.
>
> https://issues.apache.org/jira/browse/HBASE/fixforversion/12320040#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel
>
>
>
>
>
> On Tue, Jul 9, 2013 at 1:14 PM, Stack <stack@duboce.net> wrote:
>
> > I am shooting for end of July for 0.96 being 'complete'.   I would like
> to
> > make a 0.96 release in August.  We have some criticals outstanding but I
> > think we could ship even if these are not fixed in time (excepting
> > migration polish and of course remaining build fixes).  See [1.] for the
> > current list of issues.  Please re-prioritize issues as you see fit (or
> > better, move issues out of 0.95.2 if you do not think they will be done
> in
> > time).
> >
> > What to do with namespaces -- the last 0.96 'feature' -- given the above
> > timeline?  Currently it is a massive patch out on a branch.  It is still
> > not done, in want of review, and the author is going on holidays for a
> few
> > weeks soon.  My thinking as of now, going by the rate of change over the
> > last few weeks and estimating what is yet to be done, is that namespaces
> > will not make it.  I am willing to be convinced otherwise but that is how
> > it looks to me currently.
> >
> > I am going to start just disabling flakey unit tests in 0.95 from here on
> > out.  When folks get the itch, they can fix at leisure first on trunk and
> > then over in 0.95.
> >
> > What else?
> >
> > Thanks,
> > St.Ack
> >
> > 1.
> >
> https://issues.apache.org/jira/browse/HBASE/fixforversion/12320040#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel
> >
> >
> >
> > On Mon, Jun 24, 2013 at 8:45 PM, Stack <stack@duboce.net> wrote:
> >
> >> (Changed the subject)
> >>
> >> On Mon, Jun 24, 2013 at 4:04 PM, Nick Dimiduk <ndimiduk@gmail.com>
> wrote:
> >>
> >>> I want to see initial data type APIs ship out with 0.95.2. A patch for
> >>> ordered byte serialization is up (HBASE-8201) and is nearing
> >>> steady-state.
> >>> However, sershe is the only person who's left feedback. I just posted
> an
> >>> early patch for the data type API itself (HBASE-8693). It should get
> some
> >>> eyes from all manor of interested parties, but I'll settle for folk
> from
> >>> Phoenix for now.
> >>>
> >>>
> >> It would be cool if Phoenix and Kiji fellows and any one else interested
> >> would weigh in and take a look see.
> >>
> >> This does not strike me as something we should hold up the release for
> >> though.  It looks like something that could go in at any time?
> >>
> >>
> >>
> >>> Should these tasks be escalated to criticals in order to grab
> attention?
> >>>
> >>>
> >> I don't think that works going by past experience (and I don't think
> this
> >> a blocker on 0.96)
> >>
> >>
> >>
> >>> Additional comments inline.
> >>>
> >>>
> >> ...
> >>
> >>
> >>
> >>> Namespaces is the long pole and progress seems slow.  Do we hold up the
> >>> > release for them?  How can we hurry this effort along?  Swat team
> >>> descends
> >>> > on Y!?
> >>> >
> >>>
> >>> It would be a shame to not get a decision on this in for 0.96.
> >>>
> >>>
> >> Agree.  We need to get 0.96 out though.  It has been too long.
> >>
> >>
> >>
> >>>  + Is anyone testing?  Integration tests fail on ec2 build from time to
> >>> time
> >>> > [2].  Our Elliott dug in on one of the failures a few days back and
> >>> found
> >>> > legit issue w/ no retry on admin tasks (I heart hbase-it tests).  Our
> >>> unit
> >>> > test story is better [3] but there are still the odd failures.
> >>> >
> >>>
> >>> With the creation of the new list, noticing these issues is going to
> push
> >>> further back-burner. Nannying this stuff should retain focus. I'll
> >>> volunteer to track on these issues as I see them.
> >>>
> >>>
> >> Thank you Nick.
> >>
> >>
> >>
> >>> Notice though that some of the more recent failures are caused by lack
> of
> >>> disk space on the Jenkins build host.
> >>>
> >>>
> >> Oh.  Missed that.  Let me dig in.
> >>
> >>
> >> St.Ack
> >>
> >
> >
>



-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

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