Question
Intel
IN
Last activity: 9 Nov 2020 15:54 EST
Stoppage of Stream service not removing node from stream landing page.
Hi Team,
We are using Pega 8.1.3. We have a couple of stream nodes to take care of queue processsos. We have below question :
Whenever we add new nodes for stream, search and background processing; It gets automatically added to Decisioning service but on other hand when we stop the service, it does not remove that particular node from Stream portal.It shows them as "Unresponsive".
When we start a node as Stream it adds that to the Stream landing page; shouldn't it be deleting the entry on that node from the page when we stop the service, in place of showing unresponsive?
Any thought on this would be really appreciated.
Thanks & Regards,
Narhar Dev Sharma
Pegasystems Inc.
US
I see your point, but this is by design... as we expect the 'unreachable' node potentially coming up anytime. If you do not need that stream service, decommission it.
Intel
IN
Hi Kevin,
Thanks for your response.
OK !! Got it. We have to delete/decommission node from stream landing page to get rid of the unresponsive issue. Is this same acrross the other Pega upper versions as well ... like 8.4 ?
Intel
IN
In production environment we don't have access to decommission the unresponsive node as per Pega's design. How do we manage removal of unresponsive node in production?
Pegasystems Inc.
US
Stream nodes run Kafka, and each member of a Kafka cluster may have unprocessed data in its queues (stored on disk in the local kafka-data folder). Stopping a node doesn't remove it from the cluster automatically because it owns some data.
If you decommission the node, the data will be repartitioned to other stream nodes in the cluster.