Elasticsearch 1.4.0.Beta1 fails to start if Marvel plugin is installed

[bbailey1024]

I just upgraded from 1.3.2 to 1.4.0.Beta1 on one of our test servers and noticed that ES would fail to start if the Marvel plugin was installed with the following error:

[2014-10-09 20:32:52,235][INFO ][node ] [indx] version[1.4.0.Beta1], pid[14476], build[1f25669/2014-10-01T14:58:15Z]
[2014-10-09 20:32:52,236][INFO ][node ] [indx] initializing ...
[2014-10-09 20:32:52,252][INFO ][plugins ] [indx] loaded [marvel], sites [marvel]
{1.4.0.Beta1}: Initialization Failed ...

1. Tried proxying org.elasticsearch.discovery.DiscoveryService to support a circular dependency, but it is not an interface.2) IllegalStateException[This is a proxy used to support circular references involving constructors. The object we're proxying is not constructed yet. Please wait until after injection has completed to use this object.]

Remove the plugin, restart ES, and ES runs just fine.
Marvel was running fine on this system with ES 1.3.2.

Linux indx 3.12.13-gentoo_radar_2 #1 SMP Thu Mar 13 05:00:54 UTC 2014 x86_64 AMD Opteron(tm) Processor 6378 AuthenticAMD GNU/Linux
java version "1.7.0_45"
OpenJDK Runtime Environment (IcedTea 2.4.3) (Gentoo build 1.7.0_45-b31)
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)
Latest Marvel

[bleskes]

Hi @bbailey1024 , which version of marvel do you have installed? you can look at the plugin/marvel/ folder and check the jar file for a version.

[bbailey1024]

Running marvel-1.2.1.jar

[bleskes]

@bbailey1024 thx for checking. I currently have no problem with 1.4.0.Beta1 and 1.2.1, which doesn't mean they don't exist but it does mean it's subtle.

How did you install marvel? Can you post your elasticsearch.yml file as well?

[bbailey1024]

Marvel was installed using the $ES_HOME/bin/plugin -i marvel -u file:///path/to/marvel-latest.zip

elasticsearch.yml:
cluster.name: name1
node.name: name
node.master: true
node.data: true
node.local: true
index.number_of_shards: 1
index.number_of_replicas: 0
path.conf: /etc/elasticsearch
path.data: /path/to/elasticsearch/data
path.work: /path/to/elasticsearch/work
path.logs: /path/to/elasticsearch/logs
path.plugins: /usr/share/elasticsearch/plugins
bootstrap.mlockall: true
network.host: x.x.x.x
transport.tcp.port: 9300
http.port: 9200
marvel.agent.exporter.es.hosts: ["x.x.x.x:9200"]
action.destructive_requires_name: true

However, I believe I understand what the problem might relate to. This dev server was running 1.3.2. The server was moved to 1.4.0.Beta1, then moved back to 1.3.2. This generated errors due to a missing Lucene jar file (obviously). Then the developer upgraded again to 1.4.0.Beta1. It is at this point that we started experiencing this issue.

I would imagine that this flawed process resulted in the anomalous behavior. I had thought this was a fresh install at the time when I opened this ticket. We've removed the old indexes and started fresh and all works well. As it was a dev server it was easier to just remove everything and start over. Since then we cannot recreate the issue or have a test case to work with. Chalk it up to user error perhaps.