AnsweredAssumed Answered

Collector Load-balancing

Question asked by Steve_Oak on Feb 10, 2017
Latest reply on Feb 14, 2017 by Steve_Oak

Over the last several releases I have noticed more of what I would call Collector-based load-balancing. For example when a Collector goes away the other collectors notify the agent of the available collectors:

 

2/06/17 07:09:06.116 AM EST [INFO] [PO:main Mailman 2] [Manager.LoadBalancer] Allowed collectors list {30.128.190.97@5001, 30.128.133.51@5001, 30.128.190.88@5001, 30.128.133.51@5001, 30.128.132.31@5001, 30.128.133.51@5001, 30.128.132.47@5001, 30.128.133.51@5001, 30.128.133.30@5001, 30.128.133.51@5001, 30.128.190.33@5001, 30.128.133.51@5001, 30.128.190.34@5001, 30.128.133.51@5001, 30.128.190.87@5001, 30.128.133.51@5001, }@1486382946140 sent to agent mom9plvwbs002|WebSphere|PROD_C_CELL/Service_Server_01A

 

What I have noticed is that even if I specify that agents should not go to a specific collector and the weight of the collector is set to 0 (others are set and either 1500 or 2000) I am still getting agents on the collector since it is still included in the above list (with no weighting).

 

I ultimately want to remove the collector 30.128.190.97@5001 from the cluster and want it to not server any new agent metrics and want it to just server history for a period of time before removal. Right now I have set in the loadbalaning.xml:

 

<agent-collector name="va10p5069x">
        <agent-specifier>.*\|.*\|.*</agent-specifier>
        <exclude>
            <collector host="VA10P50696" port="5001"/>
            <collector host="30.128.190.97" port="5001"/>

         
        </exclude>
    </agent-collector>

 

And my MoM has

 

introscope.enterprisemanager.clustering.login.p50696.host=30.128.190.97
introscope.enterprisemanager.clustering.login.p50696.port=5001
introscope.enterprisemanager.clustering.login.p50696.weight=0
introscope.enterprisemanager.clustering.login.p50696.publickey=internal/server/EM.public

 

 

Is there an property in the EM Properties that I can set in the Collector to say not to participate in the collect/agent level communication.

 

BTW this is a 10.2 cluster and this collector was serving agent and I thought that changing above would take the agent off this server and move then to other collectors in the cluster.

 

Over the weekend I may shut the server down for an hour so to see when it comes back up if it will go thru the MoM load-balancing and not take any new agents....

Outcomes