iDash- SLA status not in sync (Load balancer)

book

Article ID: 242666

calendar_today

Updated On:

Products

iDash Workload Automation

Issue/Introduction

We installed iDash on primary and secondary server (HA). The load balancer always points to primary and switch to secondary in the event primary doesn't respond within a minute. Yesterday , the primary  URL wasn't loading and it required a service recycle -during that time, we received some SLA missed alerts - when checked, the job completed and it shouldn't have alerted . ON the primary URL , it shows that the SLA is met but on the secondary , it shows SLA missed.

How can we  fix the status sync issue?

Environment

Release : 12.1

Component : iDASH WORKLOAD AUTOMATION FOR CA 7

Resolution

Need to perform the following steps:

1. Stop both primary and secondary idash task

2. cleanup\delete all seed & delta files under the dat directory on both the Primary and Secondary machines on all CA7 instances. 

3.clean up all the SLA's in the IDASH_HOME/log/sla folder from the primary & secondary iand also in IDASH_HOME/log/sla/final and IDASH_HOME/log/sla/archive. 

4. Restart idash on primary then secondary

5. Do a data extract to bring the seed data back in, and test the connection. (This needs to be done for all CA7s instances on both iDash primary and secondary).