Does Notification Setting of v6.4 need to restart replicate instance ?

[khchoy]

Hi All,

I configured Latency Notification but it is not working .

In monitoring tab, latency is over 6 min. I set rule 300 sec. I checked repsrv.log  but log displayed like as  below all time.

00020750: 2020-06-16T14:15:53:490984 [UTILITIES ]T: Firing trigger of type 'TIMER_TRIGGER'. No parameters (notification_manager.c:1153)
00020750: 2020-06-16T14:15:53:491041 [UTILITIES ]T: Start handling of trigger of type 'TIMER_TRIGGER' (notification_manager.c:1311)
00020750: 2020-06-16T14:15:53:491072 [UTILITIES ]T: Checking on condition '$LATENCY > 300' (notification_manager.c:1353)
00020750: 2020-06-16T14:15:53:491106 [UTILITIES ]T: Check condition returns false (notification_manager.c:1506)
00020750: 2020-06-16T14:15:53:491131 [UTILITIES ]T: Checking on condition '$LATENCY > 1200' (notification_manager.c:1353)
00020750: 2020-06-16T14:15:53:491163 [UTILITIES ]T: Check condition returns false (notification_manager.c:1506)

I  did not restart instance after notification setting . 

What's wrong ?

Regards,

KH 

[Steve_Nguyen · Accepted solution]

When enable latency or disable latency monitor, i remember that you would need to stop and resume task. 

[khchoy]

Hi ,

Thank for help.  some configurations are not same working with previous version. 

And this kind of working did not explained in User guide.

Thanks.

KH