Thanks, will do that. Also, the very fact the new nodes get some data (~10gb) and then get stuck, the configurations and process I am using must be correct, and there is no immediate fix besides upgrade the version?
On Fri, Mar 20, 2015 at 4:02 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Fri, Mar 20, 2015 at 3:57 PM, Pranay Agarwal <agarwalpran...@gmail.com> > wrote: > >> I guess now, I have decide it's better to upgrade to 2.1.6+ or downgrade >> to stable release and safe way to do that. >> > > You can't downgrade across major versions, you'd have to read out > everything from the "new" cluster and write it to a different "old' cluster. > > If I were you, I would likely just prioritize upgrading to 2.1.3, and then > immediately 2.1.4 when it comes out, etc. > > =Rob > >
