Given that an upgrade is (for various internal reasons) not an option at this point...is there anything I can do to get repair working again? I'll also mention that I see this behavior from all nodes.
Thanks. On Tue, Jul 1, 2014 at 2:51 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Tue, Jul 1, 2014 at 11:09 AM, Brian Tarbox <tar...@cabotresearch.com> > wrote: > >> We're running 1.2.13. >> > > 1.2.17 contains a few streaming fixes which might help. > > >> Any chance that doing a rolling-restart would help? >> > > Probably not. > > >> Would running without the "-pr" improve the odds? >> > > No, that'd make it less likely to succeed. > > =Rob > >
