You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the multiple aggregator in same physical host implementation it was found that the host names being logged to the database when monitoring itself are storing the actual physical host name instead of the logical one provided through orcm-site configuration.
Expected Behavior
Each aggregator getting its hostname registry to database like they are registered in orcm-site logical name
Actual Behavior
Given an orcm-site with multiple aggregators and running them in the same physical node will produce database entries where hostname is the physical one instead of logical name.
If your aggregators are named agg01, agg02, etc.. and those are run under master3 node, all of the entries will be logged with master3 as the hostname.
Steps to Reproduce the Problem
Configure orcm-site like the one attached below where you have multiple aggregators.
Launch orcmsched
Run orcmd for each aggregator using the -p option like this: ./orcmd -p 55815
Verify entries in database and all of the aggregators will be using the same physical hostname registered.
Description
During the multiple aggregator in same physical host implementation it was found that the host names being logged to the database when monitoring itself are storing the actual physical host name instead of the logical one provided through orcm-site configuration.
Expected Behavior
Each aggregator getting its hostname registry to database like they are registered in orcm-site logical name
Actual Behavior
Given an orcm-site with multiple aggregators and running them in the same physical node will produce database entries where hostname is the physical one instead of logical name.
If your aggregators are named
agg01
,agg02
, etc.. and those are run undermaster3
node, all of the entries will be logged withmaster3
as the hostname.Steps to Reproduce the Problem
orcmsched
orcmd
for each aggregator using the -p option like this:./orcmd -p 55815
Specifications
The text was updated successfully, but these errors were encountered: