Incessant Technologies Pvt Ltd

Incessant Technologies Pvt Ltd
NARENDRACHAGANTI Member since 2010 7 posts
Incessant Technologies Pvt Ltd
Posted: July 5, 2016
Last activity: December 5, 2016
Posted: 5 Jul 2016 18:29 EDT
Last activity: 5 Dec 2016 12:24 EST

Elastic search uses the hazelcast configuration?



We have recently seen issue with hazelcast where it is autodiscovering the IP's on back up NIC.


We have added configuration to restrict it to look for IP's starting with '12.13.*.*'  (<env name=“cluster/hazelcast/interface” value=“IP_ADDRESS” />)which worked well.


As we are planning to leverage elastic search from Pega 7.1.9 the question here is 


1. Will elastic search use the same hazelcast configuration and use the same IP's defined or does it needs to be configured again?

2. Currently hazelcast is registering the pyClusterAddress in pr_sys_statusnodes table with port number. But it is mentioned the elastic search will use different port, does that mean it uses the IP address and ignores the port number.


For example the pyCLusterAddress column in pr_sys_statusnodes is, then elastic search will use just the IP xx.xx.xx.xx and use the ports in the range (9300-9399)

***Updated by Moderator: Marissa to remove IP address***

Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.