If there’s no technical limitation, we should definitely do it. As you note, customers running in production hate when they have to shut down clusters and with some of the testing infrastructure being rolled out, this is definitely something we can set up automated testing for. +1
-Dima On Mon, Jun 20, 2016 at 2:58 PM, Enis Söztutar <[email protected]> wrote: > Time to formalize 2.0 rolling upgrade scenario? > > 0.94 -> 0.96 singularity was a real pain for operators and for our users. > If possible we should not have the users suffer through the same thing > unless there is a very compelling reason. For the current stuff in master, > there is nothing that will prevent us to not have rolling upgrade support > for 2.0. So I say, we should decide on the rolling upgrade requirement now, > and start to evaluate incoming patches accordingly. Otherwise, we risk the > option to go deeper down the hole. > > What do you guys think. Previous threads [1] and [2] seems to be in favor. > Should we vote? > > Ref: > [1] > > http://search-hadoop.com/m/YGbbsd4An1aso5E1&subj=HBase+1+x+to+2+0+upgrade+goals+ > > [2] > > http://search-hadoop.com/m/YGbb1CBXTL8BTI&subj=thinking+about+supporting+upgrades+to+HBase+1+x+and+2+x >
