Last activity: 22 Feb 2023 21:38 EST
Externalization for Elasticsearch
Dear team- I have few questions on Externalization for Elasticsearch.
As part of documentation (https://docs.pega.com/bundle/platform-88/page/platform/deployment/client-managed-cloud/externalize-search-and-reporting.html#externalize-srs) it is mentioned that embedded mode of elastic search is not supported in version 8.8. When checked in platform support guide it says Embedded mode is still supported but deprecated. This is contradicting.
As part of container based deployment, SRS images to be used which can create elastic search workers or can connect to a external elastic search. What about applications which is not dependent elasticsearch functionality? Is it mandator to have SRS as part of deployment or can it be removed from deployment (assuming even rule search is not used)?
@ArulDevan If you don't want to use SRS and elastic search features, you don't need to install it.
Hi @SriharshaAnika: Thanks for your inputs. So PEGA will be running only with web, stream, and clustering service.
In terms of configuration, is there anything to be done other than disabling index from Search landing page?
Also is there any documentation on this (to say PEGA can run without SRS and elastic search)
Instellars Global Consulting Pvt. Ltd
You'll need to remove the Search Nodetype from your Deployment configuration if you don't need the Full Text Search option which facilitates the Searching Functionality in the Pega Application.
But May I know what you would like to achieve by removing / not using the Search Functionality through SRS or Elastic Search configuration?
Instellars Global Consulting Pvt. Ltd
I went through your post again and understood the statement. By removing the embedded Search option, Pega is trying to achieve the light weight for more faster processing capability. In that aspect, It's not applies ONLY for Search and applies for Stream Node too.
From 8.8 onwards, Pega made both Search and Stream configurations are external components through Pipelines configuration which will eventually make the Application Maintenance less and Dedicated DB connection establishment from Stream / Kafka.
Of course, there's official documentation yet on the contradictory statement yet. But, What Pega is trying to say is that, Elastic Search is Deprecated but still be supported means, eventually new versions will not be supporting the functionality as Embedded type.
I hope, i have answered your query.
Hi @KishoreSanagapalli: Agreed on the modernisation from PEGA to externalize third party components. But the main question here is do we need to deploy SRS pods if application don't need elastic search functionality.
Also on the contradicting statements, would be good if it can be rectified to avoid confusions.
Updated: 22 Feb 2023 21:38 EST
Hello leverage the helm charts given in
by default unless you enable flag in backing services "externalSearchService" as true deployment process does not look for search availability also NodeType you should remove "search" and leave the image value for PegaSearch empty - there by search deployment will not happen, engine will not look out for search image and deployment will not be dependent for search.
Hi @SriharshaAnika: Thanks for the update. Does it mean that applications are still required to deploy SRS pods (by giving empty value for ES images)?
@ArulDevan It's the standard template given which has validations performed during compile time and run time just like any other programming language. it is advised to go with empty values and necessary configuration overrides.
Hi @SriharshaAnika: Thanks for the update. Templates provided has details on whether to have elastic search as internally managed instance or as external. But the main question here is what if application don't need elastic search functionality itself. So should we still need to deploy SRS pods with empty values? (srs.srsStorage.provisionInternalESCluster=false and srs.enabled=false)
@ArulDevan If you leave the value empty pods will not get deployed
If a application is not using PEGA search functionality, then it can update the templates for SRS to give empty values for above mentioned attributes so that SRS pods and elastic search nodes will not be deployed. Also search functionality should be disabled in search landing page.
@ArulDevan Also Node type needs to be updated to remove search node