How to Pin Down The Coherence Management To A Specific Member In the Cluster?
(Doc ID 3014962.1)
Last updated on APRIL 11, 2024
Applies to:
Oracle Coherence - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Goal
When we start a Managed Coherence Cluster in WebLogic, we cannot anymore select which Coherence member will be the management node (we used to be able to do that in WLS 12.1.3.x). This is problematic to us because we want to enable an agent (prometheus) only on the management node. One way to do that is to specifically start first the node with the agent configured but this is not possible since we use automated tools to start/stop the cluster. Is there a way to pin the Coherence management capability on a specific node by configuration? We are in the process of upgrading our WLS 12.1.3.0 farm to 12.2.1.4.0.
How to Pin Down The Coherence Management To A Specific Member In the Cluster?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |