On Ignition Edge (I’m using 8.1.4), for some reason the Store and Forward web page status screen isn’t updating correctly. It continuously shows the same large amount of records needing to be sync’ed. There are no syncing errors in the log file and new data is syncing correctly to the central gateway. These pending records were accumulated during a network disconnect…and when re-connected, we did see data get pushed (although the large number of records didn’t change). The file default.idb doesn’t seem to reduce in size either. Any ideas why this would happen?
Bringing this up again as even with the latest 8.1.41 Edge version, I see a forever increasing number of records build up in the Local Storage queue. Images below are from a new Edge deployment with less than 24 hours of being live and connected to a central gateway via the gateway network. Central Gateway is running 8.1.39 and is receiving data from this Edge site just fine.
Somehow the Edge gateway isn't flushing out its records from the default.idb file.
If I stop Edge service, delete the default.idb file, then start Edge again, A new file is created and begins to forever increase in size.
One key difference between this installation and others that don't exhibit the same behavior is that this server is running full Ignition and Edge side by side. Edge is installed in separate \IgnitionEdge\ folder, service name is IgnitionEdge, and is using modified ports 8044, 8089, 8061, and 62542 (not that any of these would impact sending data out).
My understanding of the local storage count in Edge is that it is also the local history cache, and records will retire from that after 35 days. If you actually hit the 10 million, Edge will stop historizing.
I can see how that would work, but we do have other Edge installs running 8.1.20 something or even older 8.1.4 ish. Where the local storage goes back down to zero and stays at zero when the connection to the central server is up. If I close the network connection, you can see the local storage increase...then when connection is opened, data gets sent and flushes as you would expect.
Hmmm. Interesting. The 10000000 is clearly the max allowed history storage on Edge.
Ok, after spot checking other sites...they all seem to have some percentage range of Local Storage (some with negative numbers...but that's another issue I brought up already)...which suggests that yes indeed it acts as a local history cache and not a visual of what data hasn't been synced yet as I assumed based on how standard Ignition S&F works. @PGriffith mentioned this to me before on this thread [IGN-5854]Pending Records and other tags missing from Ignition Edge Store and Forward, but it didn't sink in until now (pun intended).