On Fri, Nov 14, 2014 at 3:41 AM, <[email protected]> wrote: > I'm also seing this problem when a 1.4.0 node tries joining a 1.3.4 cluster > with cloud-aws plugin version 2.4.0. Is there a workaround to use during > upgrade, since I assume it's not a problem when they're all upgraded to > 1.4.0.
I ended up starting a new cluster (ignoring all the warnings logged on startup), and restoring from a snapshot. Once all the 1.3.4 nodes were gone, no issues. -- Eric Jain Got data? Get answers at zenobase.com. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHte5%2BJ%2BfnBnus%3DOX6itdwcaB9%2Bh_KDMwDYRBWU-4fWL0CohJA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
