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
Let's consider two CBs using the same DB (typical scenario in HA configurations):
One active csub in DB
Start CB1
Start CB2
Update entity in CB1 -> notif is sent (OK)
Update entity in CB2 -> notif is sent (OK)
csub updated to inactive in CB1
Wait for a csub cache cycle
Update entity in CB1 -> notif is not sent (OK)
Update entity in CB2 -> notif is sent (NOK)
Additional info:
If we swap the role of CB1 and CB2 in the above sequence the problem is the same (but in this case CB1 is the one which fails, sending a notification that must not be sent)
If has been detected both in 3.5.1 and master
The problem doesn't occur if -noCache is used
The text was updated successfully, but these errors were encountered:
Update entity in CB2 -> notif is not sent [i.e. CB2 is back to the right behaviour]
Update entity in CB1 -> notif is sent (NOK) [i.e. CB1 previously working right now works wrong]
fgalan
changed the title
Cache status not correctly updated when several CBs are working in paralell
Cache status not correctly updated when several CBs are working in parallel
Feb 22, 2022
Let's consider two CBs using the same DB (typical scenario in HA configurations):
Additional info:
-noCache
is usedThe text was updated successfully, but these errors were encountered: