Question

JAVA Option -DExcludeAgents is not working as expected

Hi all,

The setting -DExcludeAgents doesnt seem to be working in our Multi node environment.

Pega Version
7.4

Env Type:
AWS Cloud Multi Node Cluster [Classification: WebNode, BackgroundProcessing, BIX, Search]

A portion of JVM_OPTS:
-Duser.country=AU -DExcludeAgents=PegaAESRemote:* -Djdk.tls.ephemer...

However, this configuration doesnt seem to be stopping the AES agents from running on the nodes. Is this a known issue? Has anyone got it to work?

***Moderator Edit-Vidyaranjan: Updated Platform Capability***

Correct Answer
October 10, 2019 - 1:04am

Hi,

Incase of node classification we do not support, -DExcludeAgents and -DIncludeAgent. If this configuaration is on typed node. It is not supported.

We can only disable agent schedule incase of node classification.

You can read similar issue here:

https://community1.pega.com/community/pega-support/question/exclude-agents-without-using-dexcludeagents-option

Thank You

 

Comments

Keep up to date on this post and subscribe to comments

October 10, 2019 - 1:04am

Hi,

Incase of node classification we do not support, -DExcludeAgents and -DIncludeAgent. If this configuaration is on typed node. It is not supported.

We can only disable agent schedule incase of node classification.

You can read similar issue here:

https://community1.pega.com/community/pega-support/question/exclude-agents-without-using-dexcludeagents-option

Thank You

 

October 10, 2019 - 1:25pm
Response to Shekhar_Shubham

Thanks Shekhar..

So according to the other post, the only option I have is to clear out our existing agent schedule records and disable the newly generated schedules on node types that do not need them. I’ll do that for now..

It’s strange though! Do we have any other article from Pega that explains this decision of not using the option with node classification? 

 

October 10, 2019 - 9:14pm
Response to Tarun Bolla

I am afraid I did not find any such article, but the idea of introducing Dnode and DapplicableNodeTypes was to manage most of these things from application and not from backend
https://community.pega.com/sites/default/files/help_v82/procomhelpmain.htm#engine/node-classification/eng-creating-custom-configurable-node-type-tsk.htm

Let me know if you have any other query.

October 12, 2019 - 5:24am
Response to Shekhar_Shubham

Right! For "most" of the things as you say. I was actually checking for a way to restrict certain pega agents from running at all. AES agents are an example. There are a few other OOTB ones as well..

October 12, 2019 - 6:11am
Response to Tarun Bolla

Yes, avoid touching the kernel agents as they are important for system to run and maintain.