Question
Itaú Unibanco
BR
Last activity: 1 Aug 2023 3:24 EDT
On Premises cluster looking for no longer used old machines
Hi folks, We are decommissioning our on premises infrastructure.And we want to start shutting down some virtual machines But, when we look at the logs of our active machines in the production environment, we noticed that machines that have not been used for over a year are still being sought after by the cluster. Generating similar logs like these:
2023-07-27 17:35:51,367 INFO [com.pega.dsm.dnode.impl.prpc.service.ServiceDeploymentImpl] (DataFlow-Service-PickingupRun-DF-536767:2022685, Access group: [ServDigital:ExternalService], Partitions=[16]) Aggregation.Default deployment refreshed: [MemberInfo{address=XX.XX.XX.XX, uuid=XXXXXXX-XXXXXXX-XXXXXX-XXXXXX-8b822921a530, prpcId=XXXXXcla, state=NORMAL}, MemberInfo{prpcId=XXXXXXXXcla, state=UNREACHABLE, errorMessage=Unable to reach node}, MemberInfo{address=XX.XX.XX.XX, uuid=XXXXXX-XXXXX-XXXX-XXXXX-2331e42c18d9, prpcId=XXXXXXcla, state=NORMAL}, MemberInfo{address=XX.XX.XX.XX, uuid=XXXXX-XXXXX-XXXXX-XXXXXX-ba6a93f38b74, prpcId=XXXXXXXcla, state=NORMAL}, MemberInfo{address=XX.XX.XX.XX, uuid=XXXXXX-XXXX7d-X-142edf7176f9, prpcId=XXXXXXXcla, state=NORMAL}, MemberInfo{address=XX.XX.XX.XX, uuid=XXXXXX-XXXX-XXX-XXXX-b3b1ba5ad325, prpcId=XXXXXXXcla, state=NORMAL}, MemberInfo{address=XX.XX.XX.XX, ...
We are afraid to ask for the definitive shutdown of the machine and the cluster will continue looking.
Hi folks, We are decommissioning our on premises infrastructure.And we want to start shutting down some virtual machines But, when we look at the logs of our active machines in the production environment, we noticed that machines that have not been used for over a year are still being sought after by the cluster. Generating similar logs like these:
2023-07-27 17:35:51,367 INFO [com.pega.dsm.dnode.impl.prpc.service.ServiceDeploymentImpl] (DataFlow-Service-PickingupRun-DF-536767:2022685, Access group: [ServDigital:ExternalService], Partitions=[16]) Aggregation.Default deployment refreshed: [MemberInfo{address=XX.XX.XX.XX, uuid=XXXXXXX-XXXXXXX-XXXXXX-XXXXXX-8b822921a530, prpcId=XXXXXcla, state=NORMAL}, MemberInfo{prpcId=XXXXXXXXcla, state=UNREACHABLE, errorMessage=Unable to reach node}, MemberInfo{address=XX.XX.XX.XX, uuid=XXXXXX-XXXXX-XXXX-XXXXX-2331e42c18d9, prpcId=XXXXXXcla, state=NORMAL}, MemberInfo{address=XX.XX.XX.XX, uuid=XXXXX-XXXXX-XXXXX-XXXXXX-ba6a93f38b74, prpcId=XXXXXXXcla, state=NORMAL}, MemberInfo{address=XX.XX.XX.XX, uuid=XXXXXX-XXXX7d-X-142edf7176f9, prpcId=XXXXXXXcla, state=NORMAL}, MemberInfo{address=XX.XX.XX.XX, uuid=XXXXXX-XXXX-XXX-XXXX-b3b1ba5ad325, prpcId=XXXXXXXcla, state=NORMAL}, MemberInfo{address=XX.XX.XX.XX, ...
We are afraid to ask for the definitive shutdown of the machine and the cluster will continue looking.
Is there anything we can do to stop the cluster from looking for these machines? Perhaps, some table that we need to purge the information referring to them?
Updated: 31 Jul 2023 2:03 EDT
Pegasystems Inc.
AU
Bring down the whole Cluster and clear the table pr_sys_statusNodes and see if the issue still happens.
Itau Unibanco SA
BR
These nodes do not appear in the pr_sys_statusNodes table. We have already done this solution and they keep appearing in the logs. Is there another table we can look at that contains machine data?