Question
Wipro Technologies Ltd
AU
Last activity: 5 Dec 2016 12:24 EST
Elastic search uses the hazelcast configuration?
Hi,
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 Proprietary information hidden:5702, 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***
Pegasystems Inc.
US
Hi Narendra,
If the elastic search does not select the appropriate IP you can do the following - the port range is 9300-9399
Hope this helps.
See SA-24120
The following prconfig setting allows the IP address to be set to an appropriate value.
Hi Narendra,
If the elastic search does not select the appropriate IP you can do the following - the port range is 9300-9399
Hope this helps.
See SA-24120
The following prconfig setting allows the IP address to be set to an appropriate value.
<env name="indexing/distributed/network/host" value="your_IP_address"/>
Pegasystems Inc.
AU
With elastic search, the indexing nodes open a communication port for communicate with both index-client and other indexer nodes.
As mentioned, by default, elastic looks for an available listen port in 9300-9399 range. You must validate that ports 9300-9399 are unblocked / available.
In pr_sys_Statusnodes - pyclusteraddress holds the hazelcast IP address/port, pyindexeraddress holds the elastic address/port.
With elastic search, the indexing nodes open a communication port for communicate with both index-client and other indexer nodes.
As mentioned, by default, elastic looks for an available listen port in 9300-9399 range. You must validate that ports 9300-9399 are unblocked / available.
In pr_sys_Statusnodes - pyclusteraddress holds the hazelcast IP address/port, pyindexeraddress holds the elastic address/port.
Both Elastic Search and Hazelcast are distributed technologies added to Pega 7 platform from 7.1.7 onwards. Elastic Search is meant to upgrade our full text search capabilities whereas Hazelcast is meant to improve our clustering and remote invocation capabilities.
Pegasystems
IN
But if we have multiple hosts how will the above setting work?
If there are multiple nodes on the same machine, then all of them need this setting but the port number will be chosen by each node to be different from the other. pyIndexerAddress column in pr_sys_statusnodes table will show which port number each node is using.
Areteans Technology Solutions Australia Pty Ltd.
IN
Hi,
Can full “Rule Content Search” be achieved by Pega OOTB “Search” functionalities ?
For example , we want to search the extract Rule Name and its details where a StepPage (e.g "MystepPage") , a hardcoded condition check (e.g if(X==”abc”)), parameter value passed (e.g param.EmpID) etc (all these given as input) is used throughout application.
If Pega OOTB Search functionalities provide these then please refer us how can we configure this in my application?
Pegasystems
IN
Already answered in https://collaborate.pega.com/question/elastic-search-info