What is the impact to PEGA services when external services (kafka and Elastic search) are down
Dear Community,
When we are externalizing third party services required for PEGA (Kafka and Elastic search), What will be the impact to PEGA services (lets say users and jobs) when the third party services are down (lets say for maintenance)?
Your input on this is much appreciated.
Thanks
Accepted Solution
Based on the internal validations, ES and Kafka should be treated as pre-req for PEGA. Though there will not be major impact to the system because of outage, system will not work perfect because the internal features of product will still depends on these external services.
Thanks.
@ArulDevan removing incorrect information to avoid adding confusion here, sorry about that.
Hi @PhilipShannon: Thanks for your update. Does it mean that there will be no impact to the web nodes if the search functionality is not used (case search / dedicated index for data)?
Thanks.
@ArulDevan removing incorrect information to avoid adding confusion
Hi @PhilipShannon: Not sure if you are referring to the ELK for log monitoring. The query is for the external elastic search and kafka service which is required for PEGA SRS and stream nodes (mentioned here). We are trying to evaluate the impact to PEGA service serving the users (web node) and batch process (batch nodes) when the external service is unavailable.
Thanks.
@ArulDevan sorry for the confusion, will delete my replies
Hi @ArulDevan, If Kaka servers down or out of memory then Queue processor will not work. We will get all items are as broken items.
Thanks.
Hi @DhanasekarC0202: I agree that the QP will have impact but I hope system should queue the items to the DB table when stream node is not available.
Also the query here is to understand the impact to the web users too. In a overall, will the pega (web nodes and batch nodes) will get impacted (lets say become unavailable) because of the outage in the external services?
Thanks.
Web User Nodes are accessible and User(s) may not notice any change.
However all of the QP's [OOTB and Custom QP's] are depends on the Kafka Processes, if end users are dependen on any RealTime Data Flows or QP's or Case Search etc., they will not be able to get the latest information.
Accepted Solution
Based on the internal validations, ES and Kafka should be treated as pre-req for PEGA. Though there will not be major impact to the system because of outage, system will not work perfect because the internal features of product will still depends on these external services.
Thanks.