I'm working with LiteSync and encountering an issue where the syncing status on the secondary database doesn't update correctly when a large batch of data is dumped into the primary database.
Here’s what I’ve observed:
- I am inserting around 1000 entries (each roughly 1KB in size) almost instantaneously into the primary database.
- To monitor the sync status, I use the PRAGMA sync_status command on the secondary node at 100ms intervals, checking the values of db_is_ready, sync_down_state, and sync_up_state.
- Even when the data dump occurs on the primary, the secondary node’s sync status does not reflect any change (the values remain the same as before the insertion).
- There’s no indication of a syncing state either during the sync process or after it completes successfully.
Effectively, while the data does sync correctly in the background, the secondary node’s reported sync status doesn't show any transition during this process.
Question : Is there a way to monitor and know when a sync process happen in the secondary node , especially when a considerable amounts of data is inserted to the primary ?