Upgrade from 0.16.0 to 0.16.2


(Enrique Medina Montenegro) #1

Hi Shay,

Just upgraded from 0.16.0 to 0.16.2 to take advantage of memory
optimizations and new features, and when ES starts up, I notice and extra
message in the output:

[2011-06-01 20:31:23,657][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: initializing ...
[2011-06-01 20:31:23,662][INFO ][plugins ] [Tom Thumb]
loaded []
[2011-06-01 20:31:29,009][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: initialized
[2011-06-01 20:31:29,010][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: starting ...
[2011-06-01 20:31:29,271][INFO ][transport ] [Tom Thumb]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
212.227.252.188:9300]}
[2011-06-01 20:31:32,363][INFO ][cluster.service ] [Tom Thumb]
new_master [Tom Thumb][kLY1wsVnRVmMGEDDhNpcZA][inet[/212.227.252.188:9300]],
reason: zen-disco-join (elected_as_master)
[2011-06-01 20:31:32,452][INFO ][discovery ] [Tom Thumb]
elasticsearch/kLY1wsVnRVmMGEDDhNpcZA
[2011-06-01 20:31:32,678][INFO ][http ] [Tom Thumb]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
212.227.252.188:9200]}
[2011-06-01 20:31:32,874][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: started
[2011-06-01 20:31:37,659][INFO ][gateway ] [Tom Thumb]
recovered [1] indices into cluster_state

What is that last line? Hope it's not anything serious...

Thanks.


(Shay Banon) #2

It just prints the number of indices recovered, what makes you think its serious?

On Wednesday, June 1, 2011 at 9:40 PM, Enrique Medina Montenegro wrote:

Hi Shay,

Just upgraded from 0.16.0 to 0.16.2 to take advantage of memory optimizations and new features, and when ES starts up, I notice and extra message in the output:

[2011-06-01 20:31:23,657][INFO ][node ] [Tom Thumb] {elasticsearch/0.16.2}[7414]: initializing ...
[2011-06-01 20:31:23,662][INFO ][plugins ] [Tom Thumb] loaded []
[2011-06-01 20:31:29,009][INFO ][node ] [Tom Thumb] {elasticsearch/0.16.2}[7414]: initialized
[2011-06-01 20:31:29,010][INFO ][node ] [Tom Thumb] {elasticsearch/0.16.2}[7414]: starting ...
[2011-06-01 20:31:29,271][INFO ][transport ] [Tom Thumb] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/212.227.252.188:9300 (http://212.227.252.188:9300)]}
[2011-06-01 20:31:32,363][INFO ][cluster.service ] [Tom Thumb] new_master [Tom Thumb][kLY1wsVnRVmMGEDDhNpcZA][inet[/212.227.252.188:9300]], reason: zen-disco-join (elected_as_master)
[2011-06-01 20:31:32,452][INFO ][discovery ] [Tom Thumb] elasticsearch/kLY1wsVnRVmMGEDDhNpcZA
[2011-06-01 20:31:32,678][INFO ][http ] [Tom Thumb] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/212.227.252.188:9200 (http://212.227.252.188:9200)]}
[2011-06-01 20:31:32,874][INFO ][node ] [Tom Thumb] {elasticsearch/0.16.2}[7414]: started
[2011-06-01 20:31:37,659][INFO ][gateway ] [Tom Thumb] recovered [1] indices into cluster_state

What is that last line? Hope it's not anything serious...

Thanks.


(Enrique Medina Montenegro) #3

Well, recovered sounds to me like something went wrong and I could bring it
back fortunately...

But maybe it's just my spanish character :wink:

On Wed, Jun 1, 2011 at 8:57 PM, Shay Banon shay.banon@elasticsearch.comwrote:

It just prints the number of indices recovered, what makes you think its
serious?

On Wednesday, June 1, 2011 at 9:40 PM, Enrique Medina Montenegro wrote:

Hi Shay,

Just upgraded from 0.16.0 to 0.16.2 to take advantage of memory
optimizations and new features, and when ES starts up, I notice and extra
message in the output:

[2011-06-01 20:31:23,657][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: initializing ...
[2011-06-01 20:31:23,662][INFO ][plugins ] [Tom Thumb]
loaded []
[2011-06-01 20:31:29,009][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: initialized
[2011-06-01 20:31:29,010][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: starting ...
[2011-06-01 20:31:29,271][INFO ][transport ] [Tom Thumb]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
212.227.252.188:9300]}
[2011-06-01 20:31:32,363][INFO ][cluster.service ] [Tom Thumb]
new_master [Tom Thumb][kLY1wsVnRVmMGEDDhNpcZA][inet[/212.227.252.188:9300]],
reason: zen-disco-join (elected_as_master)
[2011-06-01 20:31:32,452][INFO ][discovery ] [Tom Thumb]
elasticsearch/kLY1wsVnRVmMGEDDhNpcZA
[2011-06-01 20:31:32,678][INFO ][http ] [Tom Thumb]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
212.227.252.188:9200]}
[2011-06-01 20:31:32,874][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: started
[2011-06-01 20:31:37,659][INFO ][gateway ] [Tom Thumb]
recovered [1] indices into cluster_state

What is that last line? Hope it's not anything serious...

Thanks.


(Shay Banon) #4

I see... . Well, the log file means that you start the cluster back up, and it found and recovered 1 index from before the restart. Nothing to be alarmed about :slight_smile:

On Wednesday, June 1, 2011 at 11:13 PM, Enrique Medina Montenegro wrote:

Well, recovered sounds to me like something went wrong and I could bring it back fortunately...

But maybe it's just my spanish character :wink:

On Wed, Jun 1, 2011 at 8:57 PM, Shay Banon <shay.banon@elasticsearch.com (mailto:shay.banon@elasticsearch.com)> wrote:

It just prints the number of indices recovered, what makes you think its serious?

On Wednesday, June 1, 2011 at 9:40 PM, Enrique Medina Montenegro wrote:

Hi Shay,

Just upgraded from 0.16.0 to 0.16.2 to take advantage of memory optimizations and new features, and when ES starts up, I notice and extra message in the output:

[2011-06-01 20:31:23,657][INFO ][node ] [Tom Thumb] {elasticsearch/0.16.2}[7414]: initializing ...
[2011-06-01 20:31:23,662][INFO ][plugins ] [Tom Thumb] loaded []
[2011-06-01 20:31:29,009][INFO ][node ] [Tom Thumb] {elasticsearch/0.16.2}[7414]: initialized
[2011-06-01 20:31:29,010][INFO ][node ] [Tom Thumb] {elasticsearch/0.16.2}[7414]: starting ...
[2011-06-01 20:31:29,271][INFO ][transport ] [Tom Thumb] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/212.227.252.188:9300 (http://212.227.252.188:9300)]}
[2011-06-01 20:31:32,363][INFO ][cluster.service ] [Tom Thumb] new_master [Tom Thumb][kLY1wsVnRVmMGEDDhNpcZA][inet[/212.227.252.188:9300]], reason: zen-disco-join (elected_as_master)
[2011-06-01 20:31:32,452][INFO ][discovery ] [Tom Thumb] elasticsearch/kLY1wsVnRVmMGEDDhNpcZA
[2011-06-01 20:31:32,678][INFO ][http ] [Tom Thumb] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/212.227.252.188:9200 (http://212.227.252.188:9200)]}
[2011-06-01 20:31:32,874][INFO ][node ] [Tom Thumb] {elasticsearch/0.16.2}[7414]: started
[2011-06-01 20:31:37,659][INFO ][gateway ] [Tom Thumb] recovered [1] indices into cluster_state

What is that last line? Hope it's not anything serious...

Thanks.


(Barsk) #5
Recover has a certain alarming tone to it, I agree with Enrique on
that.


Just as a thought the word "discovered" could serve the same purpose
and not be confused about. No big deal though.




Shay Banon skrev 2011-06-02 08:20:
<blockquote cite="mid:98D5B209788B4B80A2DECC28C6FCDDA9@elasticsearch.com" type="cite">I see... . Well, the log file means that you start
        the cluster back up, and it found and recovered 1 index from
        before the restart. Nothing to be alarmed about :)

On Wednesday, June 1, 2011 at 11:13 PM, Enrique Medina Montenegro wrote:

Well, recovered sounds to me like something went wrong and I could bring it back fortunately...

But maybe it's just my spanish character :wink:

On Wed, Jun 1, 2011 at 8:57 PM, Shay Banon <shay.banon@elasticsearch.com>
wrote:

It just prints the number of indices recovered, what makes you think its serious?

On Wednesday, June 1, 2011 at 9:40 PM, Enrique Medina Montenegro wrote:

Hi Shay,

Just upgraded from 0.16.0
to 0.16.2 to take advantage
of memory optimizations and
new features, and when ES
starts up, I notice and
extra message in the output:

[2011-06-01
20:31:23,657][INFO ][node
          ] [Tom
Thumb]
{elasticsearch/0.16.2}[7414]:
initializing ...[2011-06-01
20:31:23,662][INFO
][plugins        Â
 ] [Tom Thumb] loaded [][2011-06-01
20:31:29,009][INFO ][node
          ] [Tom
Thumb]
{elasticsearch/0.16.2}[7414]:
initialized
[2011-06-01
20:31:29,010][INFO ][node
          ] [Tom
Thumb]
{elasticsearch/0.16.2}[7414]:
starting ...[2011-06-01
20:31:29,271][INFO
][transport       Â
 ] [Tom Thumb]
bound_address
{inet[/0:0:0:0:0:0:0:0:9300]},
publish_address {inet[/212.227.252.188:9300]}[2011-06-01
20:31:32,363][INFO
][cluster.service    Â
 ] [Tom Thumb] new_master
[Tom
Thumb][kLY1wsVnRVmMGEDDhNpcZA][inet[/212.227.252.188:9300]],
reason: zen-disco-join
(elected_as_master)[2011-06-01
20:31:32,452][INFO
][discovery       Â
 ] [Tom Thumb]
elasticsearch/kLY1wsVnRVmMGEDDhNpcZA[2011-06-01
20:31:32,678][INFO ][http
          ] [Tom
Thumb] bound_address
{inet[/0:0:0:0:0:0:0:0:9200]},
publish_address {inet[/212.227.252.188:9200]}
[2011-06-01
20:31:32,874][INFO ][node
          ] [Tom
Thumb]
{elasticsearch/0.16.2}[7414]:
started[2011-06-01
20:31:37,659][INFO
][gateway        Â
 ] [Tom Thumb] recovered
[1] indices into
cluster_state

What is that last line?
Hope it's not anything
serious...

                                        Thanks.
                                      </blockquote>
-- 
Med vänlig hälsning
Kristian Jörg

Devo IT AB
Tel: 054 - 22 14 58, 0709 - 15 83 42
E-post: kristian.jorg@devo.se
Webb: http://www.devo.se

(Paul Loy) #6

After I go for a run I recover. There's nothing negative about that. It's a
good thing - if I didn't recover something has gone awry :slight_smile:

Discovery has very different meanings in elastic search so that's not a good
alternative.

Personally I think recovered adequately describes what has gone on. You've
found the relevant data on the gateway, and recovered it. It's exactly what
is happening.

On Tue, Jun 7, 2011 at 3:35 PM, Kristian Jörg krjg@devo.se wrote:

Recover has a certain alarming tone to it, I agree with Enrique on that.
Just as a thought the word "discovered" could serve the same purpose and
not be confused about. No big deal though.

Shay Banon skrev 2011-06-02 08:20:

I see... . Well, the log file means that you start the cluster back up,
and it found and recovered 1 index from before the restart. Nothing to be
alarmed about :slight_smile:

On Wednesday, June 1, 2011 at 11:13 PM, Enrique Medina Montenegro wrote:

Well, recovered sounds to me like something went wrong and I could bring
it back fortunately...

But maybe it's just my spanish character :wink:

On Wed, Jun 1, 2011 at 8:57 PM, Shay Banon shay.banon@elasticsearch.comwrote:

It just prints the number of indices recovered, what makes you think its
serious?

On Wednesday, June 1, 2011 at 9:40 PM, Enrique Medina Montenegro wrote:

Hi Shay,

Just upgraded from 0.16.0 to 0.16.2 to take advantage of memory
optimizations and new features, and when ES starts up, I notice and extra
message in the output:

[2011-06-01 20:31:23,657][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: initializing ...
[2011-06-01 20:31:23,662][INFO ][plugins ] [Tom Thumb]
loaded []
[2011-06-01 20:31:29,009][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: initialized
[2011-06-01 20:31:29,010][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: starting ...
[2011-06-01 20:31:29,271][INFO ][transport ] [Tom Thumb]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
212.227.252.188:9300]}
[2011-06-01 20:31:32,363][INFO ][cluster.service ] [Tom Thumb]
new_master [Tom Thumb][kLY1wsVnRVmMGEDDhNpcZA][inet[/212.227.252.188:9300]],
reason: zen-disco-join (elected_as_master)
[2011-06-01 20:31:32,452][INFO ][discovery ] [Tom Thumb]
elasticsearch/kLY1wsVnRVmMGEDDhNpcZA
[2011-06-01 20:31:32,678][INFO ][http ] [Tom Thumb]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
212.227.252.188:9200]}
[2011-06-01 20:31:32,874][INFO ][node ] [Tom Thumb]
{elasticsearch/0.16.2}[7414]: started
[2011-06-01 20:31:37,659][INFO ][gateway ] [Tom Thumb]
recovered [1] indices into cluster_state

What is that last line? Hope it's not anything serious...

Thanks.

--
Med vänlig hälsning
Kristian Jörg

Devo IT AB
Tel: 054 - 22 14 58, 0709 - 15 83 42
E-post: kristian.jorg@devo.se
Webb: http://www.devo.se

--

Paul Loy
paul@keteracel.com
http://uk.linkedin.com/in/paulloy


(system) #7