RE: Liferay 7.3 on Docker with Elasticsearch - Connection refused

2021-01-29T14:40:29Z

Hello,

thanks! I couldn't find that - I could only find the documentation for 7.2 (https://help.liferay.com/hc/en-us/articles/360029031671-Configuring-the-Liferay-Elasticsearch-Connector). It indeed seems to be working now

Best regards

RE: Liferay 7.3 on Docker with Elasticsearch - Connection refused

2021-01-29T14:27:48Z

I believe the first thing you need to do is read the docs: Liferay and Elasticsearch

Specifically, in Connecting to Elasticsearch, you'll see that 7.3 uses the HTTP connection, whereeas you have configured the transport connection. In addition, wile configuring operationMode will still work, you might as well use the non-deprecated replacement for it, productionModeEnabled:

A simple 7.3 connector configuration enables production mode (productionModeEnabled="true") and sets the URL to each Elasticsearch node (networkHostAddresses=["http://es-node:9200"]).

RE: Liferay 7.3 on Docker with Elasticsearch - Connection refused

2021-01-29T14:16:56Z

Hello,

thanks for the answer! Is the property the same? Sadly there is no docs for 7.3 for this and also I can't see anything in breaking changes.
Below is my .config file:

operationMode="REMOTE"
transportAddresses="elasticsearch:9200"
clusterName="elasticsearch

And sadly it does not work

RE: Liferay 7.3 on Docker with Elasticsearch - Connection refused

2021-01-29T14:07:50Z

Hi, you should be using port 9200 and not 9300 in your connector config ( com.liferay.portal.search.elasticsearch7.configuration.ElasticsearchConfiguration.config file)

Since Liferay Portal/DXP 7.3 the connector uses the HTTP connection.

Hope it helps

RE: RE: Liferay 7.3 on Docker with Elasticsearch - Connection refused

2021-01-29T17:48:08Z

What I eventually did is I switched to elastic 6 and it worked...

I don't know if that solution is applicable for you. Funny enough - the documentation states that it is compatible with elastic 7...

RE: Liferay 7.3 on Docker with Elasticsearch - Connection refused

2021-01-29T12:41:31Z

Hello,

has anyone found a solution for that? I have the same issue on Liferay DXP 7.3 GA1

Best regards

Liferay 7.3 on Docker with Elasticsearch - Connection refused

2020-11-16T08:10:47Z

I have a problem with Liferay + Elasticsearch setup with docker-compose. When starting the compose bundle Liferay complains that it cannot connect to remote elasticsearch instance with exception:

&nbsp;2020-11-15 21:39:55.042 ERROR [main][ElasticsearchEngineConfigurator:93] bundle com.liferay.portal.search.elasticsearch7.impl:2.0.30 (655)[com.liferay.portal.search.elasticsearch7.internal.ElasticsearchEngineConfigurator(1604)] : The activate method has thrown an exception&nbsp;
&nbsp;java.lang.RuntimeException: java.net.ConnectException: Connection refused
&nbsp; at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.cluster.HealthClusterRequestExecutorImpl.getClusterHealthResponse(HealthClusterRequestExecutorImpl.java:102)
&nbsp; at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.cluster.HealthClusterRequestExecutorImpl.execute(HealthClusterRequestExecutorImpl.java:49)
&nbsp; at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.cluster.ElasticsearchClusterRequestExecutor.executeClusterRequest(ElasticsearchClusterRequestExecutor.java:51)
&nbsp; at com.liferay.portal.search.engine.adapter.cluster.HealthClusterRequest.accept(HealthClusterRequest.java:40)
&nbsp; at com.liferay.portal.search.engine.adapter.cluster.HealthClusterRequest.accept(HealthClusterRequest.java:22)
&nbsp; at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.cluster.ElasticsearchClusterRequestExecutor.execute(ElasticsearchClusterRequestExecutor.java:44)
&nbsp; at com.liferay.portal.search.elasticsearch7.internal.search.engine.adapter.ElasticsearchSearchEngineAdapterImpl.execute(ElasticsearchSearchEngineAdapterImpl.java:69)
&nbsp; at com.liferay.portal.search.elasticsearch7.internal.ElasticsearchSearchEngine.waitForYellowStatus(ElasticsearchSearchEngine.java:334)
&nbsp; at com.liferay.portal.search.elasticsearch7.internal.ElasticsearchSearchEngine.initialize(ElasticsearchSearchEngine.java:109)
&nbsp; at com.liferay.portal.kernel.search.SearchEngineProxyWrapper.initialize(SearchEngineProxyWrapper.java:59)
&nbsp; at com.liferay.portal.search.elasticsearch7.internal.BaseSearchEngineConfigurator.setSearchEngine(BaseSearchEngineConfigurator.java:500)
&nbsp; at com.liferay.portal.search.elasticsearch7.internal.BaseSearchEngineConfigurator.initSearchEngine(BaseSearchEngineConfigurator.java:407)
&nbsp; at com.liferay.portal.search.elasticsearch7.internal.BaseSearchEngineConfigurator.initialize(BaseSearchEngineConfigurator.java:341)
&nbsp; at com.liferay.portal.search.elasticsearch7.internal.ElasticsearchEngineConfigurator.activate(ElasticsearchEngineConfigurator.java:52)
&nbsp; &nbsp; # Loong stack trace with Casued by "java.net.ConnectException: Connection refused"

At the same time I can connect via curl to the machines and they respond:

liferay@a4b06641f395 /opt/liferay&nbsp;
$ curl es-node-1:9200
{
&nbsp; "name" : "es-node-1",
&nbsp; "cluster_name" : "docker-elasticsearch",
&nbsp; "cluster_uuid" : "iUW--n_ORe-zv40sBzUdpQ",
&nbsp; "version" : {
&nbsp; &nbsp; "number" : "7.9.3",
&nbsp; &nbsp; "build_flavor" : "default",
&nbsp; &nbsp; "build_type" : "docker",
&nbsp; &nbsp; "build_hash" : "c4138e51121ef06a6404866cddc601906fe5c868",
&nbsp; &nbsp; "build_date" : "2020-10-16T10:36:16.141335Z",
&nbsp; &nbsp; "build_snapshot" : false,
&nbsp; &nbsp; "lucene_version" : "8.6.2",
&nbsp; &nbsp; "minimum_wire_compatibility_version" : "6.8.0",
&nbsp; &nbsp; "minimum_index_compatibility_version" : "6.0.0-beta1"
&nbsp; },
&nbsp; "tagline" : "You Know, for Search"
}

liferay@a4b06641f395 /opt/liferay&nbsp;
$ curl es-node-1:9300
curl: (1) Received HTTP/0.9 when not allowed

I have following `docker-compose.yml` file:

version: '3.2'

services:
&nbsp; web:
&nbsp; &nbsp; image: liferay/portal:7.3.4-ga5
&nbsp; &nbsp; ports:
&nbsp; &nbsp; &nbsp; - "3002:8080"
&nbsp; &nbsp; depends_on:
&nbsp; &nbsp; &nbsp; - appdb
&nbsp; &nbsp; &nbsp; - liferaydb
&nbsp; &nbsp; &nbsp; - es-node-1
&nbsp; &nbsp; &nbsp; - es-node-2
&nbsp; &nbsp; environment:
&nbsp; &nbsp; &nbsp; LIFERAY_LIFERAY_PERIOD_HOME: /opt/liferay
&nbsp; &nbsp; &nbsp; LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_DRIVER_UPPERCASEC_LASS_UPPERCASEN_AME: com.mysql.cj.jdbc.Driver
&nbsp; &nbsp; &nbsp; LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_USERNAME: user
&nbsp; &nbsp; &nbsp; LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_URL: jdbc:mysql://liferaydb/liferay_db?useFastDateParsing=false
&nbsp; &nbsp; &nbsp; LIFERAY_JDBC_PERIOD_DEFAULT_PERIOD_PASSWORD: user_pass
&nbsp; &nbsp; &nbsp; LIFERAY_PASSWORDS_PERIOD_ENCRYPTION_PERIOD_ALGORITHM_PERIOD_LEGACY: SHA
&nbsp; &nbsp; &nbsp; LIFERAY_WEB_PERIOD_SERVER_PERIOD_HTTP_PERIOD_PORT: 8080
&nbsp; &nbsp; &nbsp; LIFERAY_WEB_PERIOD_SERVER_PERIOD_PROTOCOL: http
&nbsp; &nbsp; &nbsp; LIFERAY_WEB_PERIOD_SERVER_PERIOD_HOST: liferay.dev
&nbsp; &nbsp; &nbsp; LIFERAY_LIVE_PERIOD_USERS_PERIOD_ENABLED: 1
&nbsp; &nbsp; volumes:
&nbsp; &nbsp; &nbsp; - ${PWD}/static/portal-ext.properties:/opt/liferay/portal-ext.properties
&nbsp; &nbsp; &nbsp; - ${PWD}/deploy:/opt/liferay/deploy
&nbsp; &nbsp; &nbsp; - ${PWD}/data/VAADIN:/opt/liferay/tomcat/webapps/ROOT/html/VAADIN
&nbsp; &nbsp; &nbsp; - ${PWD}/static/ElasticsearchConfiguration.config:/opt/liferay/osgi/configs/com.liferay.portal.search.elasticsearch7.configuration.ElasticsearchConfiguration.config

&nbsp; appdb:
&nbsp; &nbsp; image: mysql:5.7
&nbsp; &nbsp; environment:
&nbsp; &nbsp; &nbsp; MYSQL_ROOT_PASSWORD: root_pass
&nbsp; &nbsp; &nbsp; MYSQL_DATABASE: portlet_db
&nbsp; &nbsp; &nbsp; MYSQL_USER: user
&nbsp; &nbsp; &nbsp; MYSQL_PASSWORD: user_pass
&nbsp; &nbsp; volumes:
&nbsp; &nbsp; &nbsp; - ${PWD}/data/appdb:/var/lib/mysql

&nbsp; liferaydb:
&nbsp; &nbsp; image: mysql:5.7
&nbsp; &nbsp; environment:
&nbsp; &nbsp; &nbsp; MYSQL_ROOT_PASSWORD: root_pass
&nbsp; &nbsp; &nbsp; MYSQL_DATABASE: liferay_db
&nbsp; &nbsp; &nbsp; MYSQL_USER: user
&nbsp; &nbsp; &nbsp; MYSQL_PASSWORD: user_pass
&nbsp; &nbsp; volumes:
&nbsp; &nbsp; &nbsp; - ${PWD}/data/liferaydb:/var/lib/mysql

&nbsp; es-node-1:
&nbsp; &nbsp; image: docker.elastic.co/elasticsearch/elasticsearch:7.9.3
&nbsp; &nbsp; environment:
&nbsp; &nbsp; &nbsp; - node.name=es-node-1
&nbsp; &nbsp; &nbsp; - cluster.name=docker-elasticsearch
&nbsp; &nbsp; &nbsp; - bootstrap.memory_lock=true
&nbsp; &nbsp; &nbsp; - discovery.seed_hosts=es-node-2
&nbsp; &nbsp; &nbsp; - cluster.initial_master_nodes=es-node-1,es-node-2
&nbsp; &nbsp; &nbsp; - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
&nbsp; &nbsp; ulimits:
&nbsp; &nbsp; &nbsp; memlock:
&nbsp; &nbsp; &nbsp; &nbsp; soft: -1
&nbsp; &nbsp; &nbsp; &nbsp; hard: -1
&nbsp; &nbsp; deploy:
&nbsp; &nbsp; &nbsp; resources:
&nbsp; &nbsp; &nbsp; &nbsp; limits:
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; memory: 1g
&nbsp; &nbsp; volumes:
&nbsp; &nbsp; &nbsp; - esdata1:/usr/share/elasticsearch/data
&nbsp; &nbsp; ports:
&nbsp; &nbsp; &nbsp; - 9200:9200

&nbsp; es-node-2:
&nbsp; &nbsp; image: docker.elastic.co/elasticsearch/elasticsearch:7.9.3
&nbsp; &nbsp; environment:
&nbsp; &nbsp; &nbsp; - node.name=es-node-2
&nbsp; &nbsp; &nbsp; - cluster.name=docker-elasticsearch
&nbsp; &nbsp; &nbsp; - bootstrap.memory_lock=true
&nbsp; &nbsp; &nbsp; - discovery.seed_hosts=es-node-1
&nbsp; &nbsp; &nbsp; - cluster.initial_master_nodes=es-node-1,es-node-2
&nbsp; &nbsp; &nbsp; - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
&nbsp; &nbsp; ulimits:
&nbsp; &nbsp; &nbsp; memlock:
&nbsp; &nbsp; &nbsp; &nbsp; soft: -1
&nbsp; &nbsp; &nbsp; &nbsp; hard: -1
&nbsp; &nbsp; volumes:
&nbsp; &nbsp; &nbsp; - esdata2:/usr/share/elasticsearch/data

volumes:
&nbsp; esdata1:
&nbsp; esdata2:

Contents of `portal-ext.properties` define data source for my portlet:

jdbc.ext.driverClassName=com.mysql.cj.jdbc.Driver
jdbc.ext.url=jdbc:mysql://appdb:3306/portlet_db
jdbc.ext.username=user
jdbc.ext.password=user_pass

Contents of `ElasticsearchConfiguration.config` define connection to Elastic:

operationMode=REMOTE
transportAddresses=["es-node-1:9300","es-node-2:9300"]
clusterName=docker-elasticsearch
logExceptionsOnly=true

Does anybody have any idea what is wrong? I tried with and without quotes in the `.config` file but I doesn't seem to work.