Enis, for customer already on 0.96, can they rolling restart to 0.98, and then from 0.98 rolling to 1.0?
Demai On Tue, May 27, 2014 at 2:40 PM, Enis Söztutar <[email protected]> wrote: > Inlined. > > > > > > 2014-05-27 16:10 GMT-04:00 Michael Segel <[email protected]>: > > > > > Isn’t HDP 2.1 shipping 0.98.x ? > > > > Yes. > > > > One more question: future upgrade from 0.96 -> 1.0 and 0.98 -> 1.0? > > > Rolling or not? > > > > 0.96 -> 1.0 probably won't be supported unless there is explicit interest > and work for it. I doubt that will happen. The reason is hfile v3 is > default in 1.0, but 0.96 code base cannot read hfile v3 files. This means > that rolling restarts is tricky because if a new server writes a new hfile, > old servers cannot read this, the region won't be opened and will keep > bouncing until it hits a new server. In theory it should work, but I won't > recommend doing it. > > 0.98 -> 1.0 should work with rolling restarts unless we do an explicit > decision to drop the support for some reason. I don't imagine there will be > a compelling enough reason to drop support for now. > https://issues.apache.org/jira/browse/HBASE-11164 tracks this. > > Enis > > > > > > > > > > Thank you, in advance > > > > > > > > and > > > > > > > > Best regards, > > > > Vladimir Rodionov > > > > Principal Platform Engineer > > > > Carrier IQ, www.carrieriq.com > > > > e-mail: [email protected] > > > > > > > > ________________________________________ > > > > > > > > Confidentiality Notice: The information contained in this message, > > > including any attachments hereto, may be confidential and is intended > to > > be > > > read only by the individual or entity to whom this message is > addressed. > > If > > > the reader of this message is not the intended recipient or an agent or > > > designee of the intended recipient, please note that any review, use, > > > disclosure or distribution of this message or its attachments, in any > > form, > > > is strictly prohibited. If you have received this message in error, > > please > > > immediately notify the sender and/or [email protected] and > > > delete or destroy any copy of this message and its attachments. > > > > > > > > > > > > >
