On Mon, Jul 6, 2015 at 4:59 PM, Enis Söztutar <[email protected]> wrote:
> I would put https://issues.apache.org/jira/browse/HBASE-13832 and > HBASE-13415 also in the must-have list. > > For DLR, +1 for disable. I would not be comfortable with it going enabled > by default unless it is tested throughly. > > can't-opt-out-procv2 should be fine I think. Bunch of testing went into > proc vs. The ITDDMasterFailover is running stable for some time for us > (1.1.1 code base). > > Would not being able to opt out of this break rolling upgrade from 1.0 or 1.1? > Enis > > On Sun, Jul 5, 2015 at 2:01 PM, Sean Busbey <[email protected]> wrote: > > > On Jul 5, 2015 1:36 PM, "Stack" <[email protected]> wrote: > > > > > > On Sat, Jul 4, 2015 at 4:01 PM, Sean Busbey <[email protected]> > wrote: > > > > > > > Hi Folks! > > > > > > > > I believe I've now worked through the logistics to put up the first > RC > > for > > > > 1.2.0. At the moment I'm waiting on a Procedure V2 blocker[1], which > I > > hope > > > > > > > > > May I add HBASE-14012 to the above list Sean? (Almost done) > > > > > > > Fine by me. Please make sure it is blocker priority with a fix version of > > 1.2.0. > > > > > 1.2.0 has Distributed Log Replay enabled by default. We good with this? > > > I've not done much testing with it enabled. Have others? > > > > > > > I haven't yet. I figured during RC0 I'd try to hit it hard and then file > > tickets as needed. > > > > If we leave it on we'll need docs for how to do a rolling upgrade. > > > > > 1.2.0 also has flush-by-store enabled by default. This has been tested > a > > > bunch and looks pretty good to me. > > > > > > > Good to hear, this and can't-opt-out-procv2 are my other big unknowns. > > > -- // Jonathan Hsieh (shay) // HBase Tech Lead, Software Engineer, Cloudera // [email protected] // @jmhsieh
