Some introduction – I have 3 SymmetricDS 3.11.7 container that is connected to each own database. Databases have the same structure and works on MySQL. One SymmetricDS is the Master and two another – child. For some list of tables, I created “Load Only Triggers” configuration in sym_trigger (where sync_on_update, sync_on_insert and sync_on_delete have 0 value). Also, I configured router for that table and linked it with triggers in table sym_trigger_router.
I do that configuration because I need sync this tables only via ‘Table reload request’. And to do that I run reload request for all tables that I need in same time.
After configuration I start some little test to make sure that everything works well. In the beginning everything was fine, but then in some cases a faced with some strange issue.
When it works normal, SymmetricDS collected data from all tables that need to be sync and send to my child node via one packet. But sometimes I have a problem, SymmetricDS start send and sync data to child node only one by one table whit huge delay.
I try to understand why it happened, also I try to analyze on which table or what data could be the issue reason, but I can’t, because issue happened randomly.
What I understand and analyzed that in log-file I have this error:
ERROR [master-cloud] [InitialLoadService] [master-cloud-job-15] Error while queuing initial loads StackTraceKey [SqlException:1943736719]
INFO [master-cloud] [DataExtractorService] [master-cloud-extract-default-7] Done with request 7117 to extract table table_name_1 into batches 12398 through 12398 for node 2
INFO [master-cloud] [DataExtractorService] [master-cloud-extract-default-7] Releasing 8 child extract requests that missed processing by parent node
WARN [master-cloud] [DataExtractorService] [master-cloud-extract-default-7] Failed on request 7117 to extract table table_name_1 into batches 12398 through 12398 for node 2
ERROR [master-cloud] [NodeCommunicationService] [master-cloud-extract-default-7] Failed to execute EXTRACT for node 2 and channel reload_queue StackTraceKey [SqlException:3396787583]And when I restart my Master Node SymmetricDS I have an error like: ‘Lock wait timeout exceeded; try restarting transaction’ and error with table sym_extract_request.
And to fixed that I need to run that SQL update query on my Master database:UPDATE sym_outgoing_batch SET status = 'IG' WHERE STATUS != 'OK' AND channel_id = 'reload';UPDATE sym_extract_request SET status = 'OK' WHERE STATUS = 'NE';
After that when I restart my reload request and It’s work normally. But then it happens but again due to a random number of reload request.
And I want to ask if someone faced with the same issue or someone maybe could help me understand how to fix that.
MSSQL on Linux - Symetric 3.10.4 - Field replicated is VARCHAR(200)
In the company i work for, a coworker who whas in charge of symmetricds and db Maintenance in his previous company told me he have wrote a script to renumber those id and reset the sequentials every 6 monts because they run out of ID and SymmetricDS stop working. They work with postgresql 9.6 and Symmetric 2.5
This would represent the PK so both would be valid and unique. This can be done with a transform that adds a variable transfrom to use the external id from the store node to be added to the STORE_ID col when syncing to corp.
