Re: damaged ES cluster after upgrade - serious problem - please help

2014-12-17 Thread Grzegorz K
On Wednesday, December 17, 2014 7:44:54 PM UTC+1, Mark Walkom wrote: > > Did you take a backup? > Yes I have a backup data catalog > Did you go from 0.90.0 to 1.3.4 directly? > Yes, upgrade was go from 0.90.3 to 1.3.4 directly > > On 17 December 2014 at 19:21, Peter Portante > wrote: >> >

Re: damaged ES cluster after upgrade - serious problem - please help

2014-12-17 Thread Mark Walkom
Did you take a backup? Did you go from 0.90.0 to 1.3.4 directly? On 17 December 2014 at 19:21, Peter Portante wrote: > > > > On Wednesday, December 17, 2014 9:23:28 AM UTC-5, Grzegorz K wrote: >> >> Hello, >> >> I have updated ElasticSearch from ver 0.90.3 to ver 1.3.4 ( OS - Debian >> Wheezy, de

Re: damaged ES cluster after upgrade - serious problem - please help

2014-12-17 Thread Peter Portante
On Wednesday, December 17, 2014 9:23:28 AM UTC-5, Grzegorz K wrote: > > Hello, > > I have updated ElasticSearch from ver 0.90.3 to ver 1.3.4 ( OS - Debian > Wheezy, deb package version ). > This is a cluster configuration, with 3 nodes connected to unicast. > Update was done with ElasticSearch s

damaged ES cluster after upgrade - serious problem - please help

2014-12-17 Thread Grzegorz K
Hello, I have updated ElasticSearch from ver 0.90.3 to ver 1.3.4 ( OS - Debian Wheezy, deb package version ). This is a cluster configuration, with 3 nodes connected to unicast. Update was done with ElasticSearch switched off. Afters start new verion ElasticSearch cluster health is in 'yellow' st