I just upgraded from 8.1.2 to 8.1.32. Both main and redundant gateways.
I noticed on the Redundancy page, the tagprovider-default will have a high number of Dispatched Updates/sec and will go red with a warning. I tried to lookup some info on this, but I couldn't find anything. Is this something to be worried about?
In 8.1.21, we overhauled the Redundancy Status Page in the gateway web UI to provide more insights into the state of redundancy synchronization and better visibility of key metrics.
What you're seeing in one of these new tables is the Queued vs Dispatched rate. The "dispatched" updates are, in other words, updates that have been accepted by the other gateway. When you have this rate lagging behind the "queued" updates rate (which is how quickly new updates are arriving to then be dispatched) long enough, we now show a warning+description.
If you're consistently showing warnings here, it might be a good idea to look into possible reasons. What is the network like between your primary/redundant node? Are both gateways on matching-spec systems? Are there other applications on these systems contending for CPU/Memory/Disk resources? Is your application generating too many memory tag updates for the system to reasonably keep synchronized (amidst other gateway network traffic)? There are many possible reasons things might be lagging. Support might be able to help give you more specific ideas for your particular environment and application.
Thanks for the reply. I'll looking into the items you listed.
@kcollins1 can you throw some light on what the metrics "Queued Updates/sec" and "Dispatched Updates/sec" cover - it looks like a moving average, but over how much time?
It is a one-minute moving average.
