So data is changed too quickly and replication doesn’t like it, sounds like a poor replication system to me honestly. Any half decent system wont care, it’ll just replicate the changes and that’s it.
Can’t say I’ve delved into SQL repication much, assuming TTRSS is pointing to one server, any changes should be tracked in transaction logs which are then replayed on the 2nd server.
Unless there is some kind of log limit where the volume of changes exceeds this limit. Then I’d be looking at expanding this limit somehow. Also if this is because replication is too slow to keep up, how are they connected, are you doing replication over a slow link?
You’ll need to provide a lot more info to get any kind of answer, I’ve never seen anyone run replcation for TTRSS before. How is it configured, versions, etc, etc.
Have you also tried looking up general MariaDB/SQL replication issues?, it’s unlikely to be TTRSS causing this just by the nature of how replication works…