0.15.1: WARN - jmx - Could not register object with name


(Reto) #1

Hi,

Since updating from 0.15.0 to 0.15.1 I'm getting the following warning
when startin up ES:
[WARN ][jmx ] [Leader] Could not register object
with name: {elasticsearch}:type=Leader [elasticsearch_KUw-
jkNURHi05sfMgKVlGQ],service=indices,index=twitter

I'm getting this on OSX and Ubuntu.

Reproduce:

I have no idea what it means, so I thought I'd just post it here..

Sincerely,
Reto

Startup output:
[2011-03-03 21:02:18,480][INFO ][node ] [Leader]
{elasticsearch/0.15.1}[10679]: initializing ...
[2011-03-03 21:02:18,484][INFO ][plugins ] [Leader]
loaded []
[2011-03-03 21:02:21,135][INFO ][node ] [Leader]
{elasticsearch/0.15.1}[10679]: initialized
[2011-03-03 21:02:21,136][INFO ][node ] [Leader]
{elasticsearch/0.15.1}[10679]: starting ...
[2011-03-03 21:02:21,221][INFO ][transport ] [Leader]
bound_address {inet[/0.0.0.0:9300]}, publish_address {inet[/
10.0.1.30:9300]}
[2011-03-03 21:02:24,348][INFO ][cluster.service ] [Leader]
new_master [Leader][KUw-jkNURHi05sfMgKVlGQ][inet[/10.0.1.30:9300]],
reason: zen-disco-join (elected_as_master)
[2011-03-03 21:02:24,404][INFO ][discovery ] [Leader]
elasticsearch/KUw-jkNURHi05sfMgKVlGQ
[2011-03-03 21:02:25,261][INFO ][cluster.metadata ] [Leader]
[twitter] creating index, cause [gateway], shards [5]/[1], mappings
[user]
[2011-03-03 21:02:25,695][INFO ][cluster.metadata ] [Leader]
[twitter] created and added to cluster_state
[2011-03-03 21:02:25,702][INFO ][http ] [Leader]
bound_address {inet[/0.0.0.0:9200]}, publish_address {inet[/
10.0.1.30:9200]}
[2011-03-03 21:02:25,703][WARN ][jmx ] [Leader]
Could not register object with name: {elasticsearch}:type=Leader
[elasticsearch_KUw-jkNURHi05sfMgKVlGQ],service=indices,index=twitter
[2011-03-03 21:02:25,704][INFO ][node ] [Leader]
{elasticsearch/0.15.1}[10679]: started


(Shay Banon) #2

It means that it failed to registered itself with JMX (which is a JVM thingy that exposes information, elasticsearch registers itself with some specific elasticsearch metrices). I think its because it uses a name that is malformed, I will check and report back.
On Thursday, March 3, 2011 at 10:05 PM, Reto wrote:

Hi,

Since updating from 0.15.0 to 0.15.1 I'm getting the following warning
when startin up ES:
[WARN ][jmx ] [Leader] Could not register object
with name: {elasticsearch}:type=Leader [elasticsearch_KUw-
jkNURHi05sfMgKVlGQ],service=indices,index=twitter

I'm getting this on OSX and Ubuntu.

Reproduce:

I have no idea what it means, so I thought I'd just post it here..

Sincerely,
Reto

Startup output:
[2011-03-03 21:02:18,480][INFO ][node ] [Leader]
{elasticsearch/0.15.1}[10679]: initializing ...
[2011-03-03 21:02:18,484][INFO ][plugins ] [Leader]
loaded []
[2011-03-03 21:02:21,135][INFO ][node ] [Leader]
{elasticsearch/0.15.1}[10679]: initialized
[2011-03-03 21:02:21,136][INFO ][node ] [Leader]
{elasticsearch/0.15.1}[10679]: starting ...
[2011-03-03 21:02:21,221][INFO ][transport ] [Leader]
bound_address {inet[/0.0.0.0:9300]}, publish_address {inet[/
10.0.1.30:9300]}
[2011-03-03 21:02:24,348][INFO ][cluster.service ] [Leader]
new_master [Leader][KUw-jkNURHi05sfMgKVlGQ][inet[/10.0.1.30:9300]],
reason: zen-disco-join (elected_as_master)
[2011-03-03 21:02:24,404][INFO ][discovery ] [Leader]
elasticsearch/KUw-jkNURHi05sfMgKVlGQ
[2011-03-03 21:02:25,261][INFO ][cluster.metadata ] [Leader]
[twitter] creating index, cause [gateway], shards [5]/[1], mappings
[user]
[2011-03-03 21:02:25,695][INFO ][cluster.metadata ] [Leader]
[twitter] created and added to cluster_state
[2011-03-03 21:02:25,702][INFO ][http ] [Leader]
bound_address {inet[/0.0.0.0:9200]}, publish_address {inet[/
10.0.1.30:9200]}
[2011-03-03 21:02:25,703][WARN ][jmx ] [Leader]
Could not register object with name: {elasticsearch}:type=Leader
[elasticsearch_KUw-jkNURHi05sfMgKVlGQ],service=indices,index=twitter
[2011-03-03 21:02:25,704][INFO ][node ] [Leader]
{elasticsearch/0.15.1}[10679]: started


(system) #3