According to org.jumpmind.symmetric.common.ParameterConstants, the correct name of this setting is without a 'd' at the end, so file.sync.enable (at least in 3.9.16). Should I also explicitly set start.file.sync.tracker.job to true and activate the corresponding push and pull jobs?
In my case these obsolete loads were in the table sym_table_reload_request - I wonder why this rubbish is not cleaned up automatically, when the node with that id is not registered or anything. I recently upgraded from SymmerticDS version 3.5.19 to version 3.9.16
In my case these obsolete loads were in the table sym_table_reload_request - I wonder why this rubbish is not cleaned up automatically, when the node with that id is not registered or anything. I'm working with SymmerticDS version 3.9.16
Hello, We are using symmeticDS in a Spring-based webapp along with a database migration tool called Flyway. 'Whenever we roll out a new version not all slave nodes synchronize smoothly and I end up re-initializing some of them. My suspicion is that the migration of the database structure should not happen while synchronization is active. So my question to you is what would be the recommended procedure for deploying a new version of a software that uses both SymmetricDS and a database migration tool...