Rob_Jago Member since 2015 41 posts
Posted: 4 years ago
Last activity: 2 years 6 months ago

More details on Elastic Search in multi node environment when the primary search node is shutdown/crashes


I am trying to find out more information about how Pega (7.1.8) and ElasticSearch work together when the primary search node (for ElasticSearch) in a multi-node environment (with a load balancer in front) goes down for one of the following scenarios:

1. it's taken offline during a migration of code, hotfix, pega upgrade, OS patches, etc.. planned offline/outage (say 1 hour at most)

2. it unexpected crashes overnight and is unavailable for hours

So, with the following scenarios above:

1. How does the searching supposed to work on node 2+ when this occurs; is this just adding the multiple nodes to the search list?

2. Does the environment re-elect a primary search node ? or does it wait until the primary comes back online? What happens if a new node has been built to replace the node that crashed (and hence, a new node ID ) which would mean the original primary search node will never be re-added back to the node list..

3. My fear is that there is manual intervention required (in particular item 2). Please ensure me there's no manual intervention required!

thank you


***Updated by moderator: Lochan to add Categories***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Low-Code App Development Data Integration
Moderation Team has archived post
Share this page LinkedIn