ES 1.3.4: sometimes plugins return empty page

Elastic Stack Elasticsearch
1

Some days ago I updated my 2-node ES Cluster to 1.3.4. Since the update the
installed plugins sometimes are not applicable and for
http://localhost:9200/_plugin/head returns an empty page.

This effect is seen very often after restarting a node, e.g. after SHUTDOWN
or simply killing the server process. After restart the ES cluster itself
runs an is applicable to ES java client, but none of the installed plugins
is applicable. Looks like the ES server does not deliver the plugins web
resources. When opening the index.html from head-plugin from filesystem,
the plugin runs fine.

Probably an issue with 1.3.4? My experience with earlier releases indicated
a very fault tolerant cluster, but with current release there are much
issues to plugin availablity.

Any ideas?

Markus

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/85cbbf81-9874-4567-99ca-6b8eed74d48f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

Anyone an idea regarding to this issue? Seems an ungraceful ES shutdown
affects the installed ES plugins ...

Some days ago I updated my 2-node ES Cluster to 1.3.4. Since the update the

installed plugins sometimes are not applicable and for
http://localhost:9200/_plugin/head returns an empty page.

This effect is seen very often after restarting a node, e.g. after
SHUTDOWN or simply killing the server process. After restart the ES cluster
itself runs an is applicable to ES java client, but none of the installed
plugins is applicable. Looks like the ES server does not deliver the
plugins web resources. When opening the index.html from head-plugin from
filesystem, the plugin runs fine.

Probably an issue with 1.3.4? My experience with earlier releases
indicated a very fault tolerant cluster, but with current release there are
much issues to plugin availablity.

Any ideas?

Markus

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7f343b0e-d423-43a6-95d4-1a0eea008e9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

I've just upgraded to 1.3.4 and no problems with plugins. I upgraded
bigdesk to 2.5.0 and cloud-aws to 2.3.0 as needed for ES 1.3.4. Have you
checked you are running latest version of head?

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/47595127-623e-43be-8f1e-b1e4b0bb42bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

4

Got it! I am using the ES java client, which becomes member of the ES
cluster. The start order is essential, when starting the client before the
server, it occupies the port 9200. There server will use the next free
port. So localhost:9200 will reach the client, which has no plugin
installed. An invalid plugin url will result in empty page.

Some days ago I updated my 2-node ES Cluster to 1.3.4. Since the update the

installed plugins sometimes are not applicable and for
http://localhost:9200/_plugin/head returns an empty page.

This effect is seen very often after restarting a node, e.g. after
SHUTDOWN or simply killing the server process. After restart the ES cluster
itself runs an is applicable to ES java client, but none of the installed
plugins is applicable. Looks like the ES server does not deliver the
plugins web resources. When opening the index.html from head-plugin from
filesystem, the plugin runs fine.

Probably an issue with 1.3.4? My experience with earlier releases
indicated a very fault tolerant cluster, but with current release there are
much issues to plugin availablity.

Any ideas?

Markus

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/80c8366b-7a84-4148-a8d5-8925d21f4e71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.