Question
Maantic Inc
US
Last activity: 11 Apr 2021 10:07 EDT
Pega V822 Agent schedule instance failed to show hostname
Hi,
Production application running in multi node environment.
Agent schedule instance are failed to show hostname, it shows value N/A.
Four node configured with node type background processing - all four nodes creates only one agent schedule instance, because of this issue, we are not able to control agent to run in specific node level.
Same configuration we had in pega 7, it created agent schedule instance for each node by having proper hostname.
Let us know what configuration changes required to get hostname in agent schedule instance
Pegasystems Inc.
US
Please check below pdn link:
https://community.pega.com/support/support-articles/host-name-displays-na-nodes-tab-agents-rule
Maantic Inc
US
resolution shows : Here’s the explanation for the reported behavior: One data instance is created for one node type. Hence, the hostnames do not display.
Can you elaborate more on it?
Maantic Inc
US
yes Kevin, this is what we are doing today.
After every restart someone need to monitor and update through admins studio, else agents will run in all the nodes.
But it is not preferred option when application has more than 100+ agents
Radial Inc
US
Hi, We are also having the same issue. It is not creating agent schedule instances for each node instead it is creating for each node type.
Can you please post how did you get resolved?
Radial Inc
US
we got an alternative way to manage the agents on each node without depending on Agent Schedule rules.
However, I am still curious why it is not creating individual schedule instances for each node. Any comments on this pls?
Maantic Inc
US
@OmprakashE8365 We are created custom node name by updating dnode. Agent aligned to run in each custom node.
it solved the issue.
Wells Fargo
US
@JohnPaulRaja,C Hi, could you please provide more details about your solution ? We are facing the same issue after our upgrade.