I am having an issue with sending Marvel stats to our monitoring cluster,
which is in Microsoft Azure. We have a production cluster on premise, a
monitoring cluster in Azure, and a working VPN between them. I am able to
access the Marvel Dashboard of the monitoring cluster from both of the
production ES servers. The access lists allow the full IP stack between
each server. I am getting this error though on our prod servers:
[2014-04-22 07:05:03,359][ERROR][marvel.agent.exporter] [VERFY-MSPSVC02]
could not connect to any configured elasticsearch instances:
[VERIFY-AZ-SVC01:9200] [2014-04-22
07:05:03,370][ERROR][marvel.agent.exporter] [VERFY-MSPSVC02] error
connecting to [VERIFY-AZ-SVC01:9200] java.net.SocketTimeoutException:
connect timed out
Can you access the monitoring cluster from the command line using telnet
when logged in on the production machine? All marvel does is an HTTP POST
call..
Cheers,
Boaz
On Tuesday, April 22, 2014 5:13:29 PM UTC+2, Mario Rodriguez wrote:
I am having an issue with sending Marvel stats to our monitoring cluster,
which is in Microsoft Azure. We have a production cluster on premise, a
monitoring cluster in Azure, and a working VPN between them. I am able to
access the Marvel Dashboard of the monitoring cluster from both of the
production ES servers. The access lists allow the full IP stack between
each server. I am getting this error though on our prod servers:
[2014-04-22 07:05:03,359][ERROR][marvel.agent.exporter] [VERFY-MSPSVC02]
could not connect to any configured elasticsearch instances:
[VERIFY-AZ-SVC01:9200] [2014-04-22
07:05:03,370][ERROR][marvel.agent.exporter] [VERFY-MSPSVC02] error
connecting to [VERIFY-AZ-SVC01:9200] java.net.SocketTimeoutException:
connect timed out
Wednesday, April 23, 2014 7:54:50 AM UTC-5, Boaz Leskes wrote:
Can you access the monitoring cluster from the command line using telnet
when logged in on the production machine? All marvel does is an HTTP POST
call..
Just double checking - can you gist the marvel config part of your
elasticsearch.yml? the way it's pasted here will not be valid..
On Friday, April 25, 2014 10:16:31 PM UTC+2, Mario Rodriguez wrote:
Wednesday, April 23, 2014 7:54:50 AM UTC-5, Boaz Leskes wrote:
Can you access the monitoring cluster from the command line using telnet
when logged in on the production machine? All marvel does is an HTTP POST
call..
One other thing I thought about - do you get this error all the time or
does appear every once in a while? Said differently, do you have data in
your monitoring cluster?
If so, you can try increasing the timeout (defaults to 6s):
marvel.agent.exporter.es.timeout: 30s
This can be done through the yml file or via the Cluster Update Settings
API :
Cheers,
Boaz
On Fri, Apr 25, 2014 at 11:15 PM, Mario Rodriguez starrio@gmail.com wrote:
Can you check and see if it helps? (you can remove the 30s setting)
Cheers,
Boaz
On Sunday, April 27, 2014 10:12:31 PM UTC+2, Boaz Leskes wrote:
Hi Mario,
Gists look good to me.
One other thing I thought about - do you get this error all the time or
does appear every once in a while? Said differently, do you have data in
your monitoring cluster?
If so, you can try increasing the timeout (defaults to 6s):
marvel.agent.exporter.es.timeout: 30s
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.