srsRuntime replica count for backingservices
We are migrating our Pega Application(V 8.6.1) which is currently running as a Weblogic on Oracle DB setup to Openshift Container(on same Oracle DB). For configuring the srs(Search and Reporting Service), do we need to keep the srsRuntime.replicaCount and replicas count in elasticsearch/values.yaml same? Can someone clarify on the same. Thanks!
Accepted Solution
Updated: 28 Dec 2023 10:44 EST
Pegasystems Inc.
US
The srsRuntime.replicaCount setting only impacts the number of SRS pods deployed and does not need to be kept in sync with the replica count in the elasticsearch values.yaml file.
CSC
US
@NickLoving_GCS Thanks Nick for your response. is the indices stored at mmapfs directory of srs pods? if yes, is it better to have more than 1 for resiliency?
Pegasystems Inc.
US
@Jey2705the SRS pods aren't storing indices, the Elasticsearch pods will store the indices. SRS acts as a bridge between the Pega application and Elasticsearch servers. Having additional SRS pods will allow for more throughput of search and indexing requests along with additional redundancy.