ES 1.1.1 - Plugins _site not found


(Dan Spinner) #1

Has anyone else ran into this?

We didn't have this behavior on 90.5. While testing out 1.1.1 it seems to
happen every minute in the logs for both of the plugins we use which are
siteless. If i create an empty _site directory for the plugins then the
log entries immediately stop. I've also confirmed that elasticsearch does
start up properly with the empty _site directory. I couldn't find anything
in the documentation about changes to plugins and the _site directory.
Curious if anyone else has experienced this, and what they did.

/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.

--
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/dcae4d4b-3f57-4e86-a18f-6ab021470b97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #2

Are you using Marvel or any other monitoring tool?

Something which call nodes info API for example???

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 31 mai 2014 à 16:23, Dan Spinner dan.spinner@sonian.net a écrit :

Has anyone else ran into this?

We didn't have this behavior on 90.5. While testing out 1.1.1 it seems to happen every minute in the logs for both of the plugins we use which are siteless. If i create an empty _site directory for the plugins then the log entries immediately stop. I've also confirmed that elasticsearch does start up properly with the empty _site directory. I couldn't find anything in the documentation about changes to plugins and the _site directory. Curious if anyone else has experienced this, and what they did.

/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.

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/dcae4d4b-3f57-4e86-a18f-6ab021470b97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/8967B355-F781-455D-AC72-B7CA408A30B5%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.


(Jörg Prante) #3

Each time you start a node, may it be a (transport) client node or a server
node, all plugins are checked/loaded at initialization.

Each plugin, also jvm plugins on the classpath, is by default examined if a
directory named "_site" can be accessed. The purpose is to classify a
plugin as site plugin. A method in FIleSystemUtils logs if the directory
has problems. So the log message is completely harmless, especially for jvm
plugins without a _site.

Note, if you see this every minute, you should research if there is
something running in your ES that initiates a (client) node at that
frequency. In most cases, this is not required.

Jörg

On Sat, May 31, 2014 at 4:23 PM, Dan Spinner dan.spinner@sonian.net wrote:

Has anyone else ran into this?

We didn't have this behavior on 90.5. While testing out 1.1.1 it seems
to happen every minute in the logs for both of the plugins we use which are
siteless. If i create an empty _site directory for the plugins then the
log entries immediately stop. I've also confirmed that elasticsearch does
start up properly with the empty _site directory. I couldn't find anything
in the documentation about changes to plugins and the _site directory.
Curious if anyone else has experienced this, and what they did.

/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.

--
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/dcae4d4b-3f57-4e86-a18f-6ab021470b97%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/dcae4d4b-3f57-4e86-a18f-6ab021470b97%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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/CAKdsXoFnEbefQrmiQWNw41KutwKGTcNfJ0A6_K3qU1vUAjqD0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(Ivan Brusic) #4

I ran into the same issue when I upgraded to 1.x. The code in the plugin
service will scan the plugins every minute. You can either disable the
lookup or reduce the logging level (which is what I did).

--
Ivan
On May 31, 2014 7:23 AM, "Dan Spinner" dan.spinner@sonian.net wrote:

Has anyone else ran into this?

We didn't have this behavior on 90.5. While testing out 1.1.1 it seems
to happen every minute in the logs for both of the plugins we use which are
siteless. If i create an empty _site directory for the plugins then the
log entries immediately stop. I've also confirmed that elasticsearch does
start up properly with the empty _site directory. I couldn't find anything
in the documentation about changes to plugins and the _site directory.
Curious if anyone else has experienced this, and what they did.

/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.

--
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/dcae4d4b-3f57-4e86-a18f-6ab021470b97%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/dcae4d4b-3f57-4e86-a18f-6ab021470b97%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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/CALY%3DcQCMt%3DkwfyZG5ty7N4Qme9Lh0UVq8yjzcM31ZyZY9Y971Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(Dan Spinner) #5

Thanks for the tip. Found that our Sensu monitoring is doing some api
calls for monitoring cluster health that are triggering the log entry.
Mystery solved. Thank you.

On Saturday, May 31, 2014 11:23:14 AM UTC-4, David Pilato wrote:

Are you using Marvel or any other monitoring tool?

Something which call nodes info API for example???

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 31 mai 2014 à 16:23, Dan Spinner <dan.s...@sonian.net <javascript:>> a
écrit :

Has anyone else ran into this?

We didn't have this behavior on 90.5. While testing out 1.1.1 it seems
to happen every minute in the logs for both of the plugins we use which are
siteless. If i create an empty _site directory for the plugins then the
log entries immediately stop. I've also confirmed that elasticsearch does
start up properly with the empty _site directory. I couldn't find anything
in the documentation about changes to plugins and the _site directory.
Curious if anyone else has experienced this, and what they did.

/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.

--
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/dcae4d4b-3f57-4e86-a18f-6ab021470b97%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/dcae4d4b-3f57-4e86-a18f-6ab021470b97%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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/fbcfb868-14ac-4320-9481-189c6c5c6f6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #6

This could help: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-info.html#cluster-nodes-info

if your plugin data is subject to change use plugins.info_refresh_interval to change or disable the caching interval:

Change cache to 20 seconds

plugins.info_refresh_interval: 20s

Infinite cache

plugins.info_refresh_interval: -1

Disable cache

plugins.info_refresh_interval: 0

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 31 mai 2014 à 20:52, Dan Spinner dan.spinner@sonian.net a écrit :

Thanks for the tip. Found that our Sensu monitoring is doing some api calls for monitoring cluster health that are triggering the log entry. Mystery solved. Thank you.

On Saturday, May 31, 2014 11:23:14 AM UTC-4, David Pilato wrote:
Are you using Marvel or any other monitoring tool?

Something which call nodes info API for example???

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 31 mai 2014 à 16:23, Dan Spinner dan.s...@sonian.net a écrit :

Has anyone else ran into this?

We didn't have this behavior on 90.5. While testing out 1.1.1 it seems to happen every minute in the logs for both of the plugins we use which are siteless. If i create an empty _site directory for the plugins then the log entries immediately stop. I've also confirmed that elasticsearch does start up properly with the empty _site directory. I couldn't find anything in the documentation about changes to plugins and the _site directory. Curious if anyone else has experienced this, and what they did.

/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:38:52 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#3]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/valve/_site] directory does not exist.
/var/log/es.log:May 23 00:39:09 localhost ES: DEBUG | [elasticsearch[Adversary][management][T#5]] | plugins | [Adversary] [/mnt/es/plugins/jetty/_site] directory does not exist.

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/dcae4d4b-3f57-4e86-a18f-6ab021470b97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/fbcfb868-14ac-4320-9481-189c6c5c6f6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/EC93B669-2B8B-4B71-9359-BE6D5A9C3824%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.


(system) #7