Solved
Best practice to start/stop nodes in a cluster
we have cluster with multiple nodes. is there any best practice or sequence to start or stop nodes in a cluster by their type for version Pega'23.
in earlier version.
Nodes should be started in the following order:
- Primary search node
- Secondary search nodes, after the primary node has started
- Remaining nodes
***Edited by Moderator Rupashree S. to add Capability tags***
To see attachments, please log in.
Accepted Solution
Posted: 7 months ago
Updated: 7 months ago
Updated: 26 Apr 2024 11:08 EDT
Maantic Inc
Maantic Inc
IN
Based on the discussion here, its mentioned that a Pega infrastructure specialist mentioned there points to follow during startup:
Bring Up:
- Background Node 1 (BackgroundProcessing, Search, Stream, WebUser)
- use the Web UI to verify the search index has finished building before continuing. I have not found a way to programmatically confirm search is finished building
- Background Node 2 (BackgroundProcessing, Search, Stream)
- Decisioning Node 1 (DDS, ADM, RTDG, Batch, RealTime)
- You must have port 7000 open for Cassandra but it is not in the documentation
- Decisioning Node 2 (DDS, ADM, RTDG, Batch, RealTime)
- Decisioning Node 3 (DDS, ADM, RTDG, Batch, RealTime)
- Web Node 1 (WebUser)
- Web Node 2 (WebUser)
Bring down in the opposite order.