<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Answers to: Multiple ElasticSearch on same machine (multiple ivy engines)</title><link>https://answers.axonivy.com/questions/3126/multiple-elasticsearch-on-same-machine-multiple-ivy-engines</link><description>&lt;p&gt;Hi ivyteam&lt;/p&gt;
&lt;p&gt;My team has a server which has 3 instances of Ivy engine on it. Sometime when we restart engine, it cause issue that "ES can not be started. Connection refused"&lt;/p&gt;
&lt;p&gt;As far as i know on each engine it sill contain one ES and it will be started when engine is started. By default, ES will take port &lt;code&gt;9200&lt;/code&gt; or &lt;code&gt;19200&lt;/code&gt; on &lt;code&gt;localhost&lt;/code&gt; (Reference link &lt;a href="https://developer.axonivy.com/doc/latest/EngineGuideHtml/installation.html#installation.elasticsearch"&gt;https://developer.axonivy.com/doc/latest/EngineGuideHtml/installation.html#installation.elasticsearch&lt;/a&gt; )&lt;/p&gt;
&lt;p&gt;So is there any cases that the port is conflicted in my situation? If so, how can we configure the port for many instance of Ivy engine? We're using Amazon cloud so it's not a good way to buy different server for each Engine on cloud.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;</description><atom:link href="https://answers.axonivy.com/questions/3126/multiple-elasticsearch-on-same-machine-multiple-ivy-engines" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 19 Mar 2018 07:55:22 -0400</lastBuildDate><item><title>Answer by Reguel Wermelinger</title><link>https://answers.axonivy.com/questions/3126/multiple-elasticsearch-on-same-machine-multiple-ivy-engines/3134</link><description>&lt;p&gt;You can set the URL to your elastic search server with a system property: Elasticsearch.ExternalServer.Url
then ivy does not start an elastic search instance by a random port...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Reguel Wermelinger</dc:creator><pubDate>Mon, 19 Mar 2018 07:55:22 -0400</pubDate><guid>https://answers.axonivy.com/questions/3126/multiple-elasticsearch-on-same-machine-multiple-ivy-engines/3134</guid></item><item><title>Answer by ToanLC</title><link>https://answers.axonivy.com/questions/3126/multiple-elasticsearch-on-same-machine-multiple-ivy-engines/3128</link><description>&lt;p&gt;Hi &lt;a href="https://answers.axonivy.com/users/118/trungdv"&gt;&lt;a href="https://answers.axonivy.com/users/118/trungdv"&gt;@trungdv&lt;/a&gt;&lt;/a&gt;,&lt;/p&gt;
&lt;p&gt;Based on my experience with Elasticsearch on Ivy, I used to try to block ES from starting on port &lt;code&gt;9200&lt;/code&gt; or &lt;code&gt;19200&lt;/code&gt; then I see that ES will try to start on another port like &lt;code&gt;9201&lt;/code&gt; or &lt;code&gt;19201&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;In addition to that, normally an Amazon EC2 instance does not allow any other port than 80, 443 or 8080. It could be refused by the firewall.&lt;/p&gt;
&lt;p&gt;You can use process explorer to check all the process and port that ES starting on. Hope it helps&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ToanLC</dc:creator><pubDate>Fri, 16 Mar 2018 00:57:12 -0400</pubDate><guid>https://answers.axonivy.com/questions/3126/multiple-elasticsearch-on-same-machine-multiple-ivy-engines/3128</guid></item></channel></rss>