back-fill doesn’t work on reconnecting to the Backend

English Forum
1

Hello dear community,

I’ve enabled Timedata.Rrd4j on my Edge (persistencePriority=MEDIUM, channels are HIGH), even reduced DELAY_TRIGGER_TIME to 10 s and MAX_RANDOM_DELAY to 60 s, but after reconnect back-fill still doesn’t work and my backend DB has gaps, what could be causing this?

Thank you.

2

I would assume, that you do not have AggregatedInfluxDB enabled.
You need some preconditions:

  1. on edge you need RRD4J enabled
  2. on backend you need AggregatedInfluxDB enabled (and added to TimedataManager)

The edge cyclically collects data within RRD4J. If the edge was disconnected from the backend it cyclically tries to reconnect to the backend. After successfully establishing a connection to the backend the missing data will be transmitted to the backend within 1h after the connection was newly established. The missing data will be send as, i think ResendDataNotification. The TimedataManager distributes them to all Databases which can handle ResendDataNotification. This is right now only the AggregatedInfluxDB .

Note that working with AggregatedInfluxDB is a bit more complicated than working with default InfluxDB. It has a lot of advantages, but you may need to invest more time to get it up and running completely.

1 Like