Thanks guys. We went with rolling upgrade since we couldn't redo the upgrade test on our test and staging envs. They were already upgraded in rolling fashion and we didn't want to spend cycles redoing the test for downtime upgrade again.
If this is possible, it would have been nice to have had the documentation say downtime upgrade is ok. maybe its widely understood that downtime upgrade is ok? But it was a bit confusing when it was mentioned on some upgrade versions but not others. Praveen On Wed, May 13, 2020 at 8:51 AM Israel Ekpo <israele...@gmail.com> wrote: > It would be a good idea to attempt this upgrade in a different environment > like QA or STAGING to make sure there are no surprises first before > upgrading PRODUCTION > > Going from 0.10 to 2.3.x is a significant jump with potential for issues > > Running a trial in a lower environment with exact setup as PROD will > prepare you better for a production upgrade experience > > > > On Wed, May 13, 2020 at 3:27 AM M. Manna <manme...@gmail.com> wrote: > > > I have done this before. What Matthias said below is correct. > > > > First you’ve got to stop all apps to prevent data consumption (if that’s > > what you also mean by having downtime) > > > > Then, you can go ahead and replace the bin. > > > > Regards, > > > > On Tue, 12 May 2020 at 18:33, Matthias J. Sax <mj...@apache.org> wrote: > > > > > I guess you can just stop all servers, update the binaries (and > > > potentially configs), and afterward restart the servers. > > > > > > Of course, you might want to stop all applications that connect to the > > > cluster first. > > > > > > > > > -Matthias > > > > > > On 5/11/20 9:50 AM, Praveen wrote: > > > > Hi folks, > > > > > > > > I'd like to take downtime to upgrade to 2.3.x from 10.2.1. But I > can't > > > find > > > > it in the doc for 2.3.x upgrade that I can take downtime to do this. > > The > > > > instructions are for rolling upgrade only. > > > > > > > > Has anyone tried this? > > > > > > > > Praveen > > > > > > > > > > > > >
