View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002819SymmetricDSBugpublic2016-09-22 07:522016-09-22 11:43
Reporterwrygiel Assigned To 
Prioritynormal 
Status closedResolutionduplicate 
Product Version3.8.3 
Summary0002819: Random conflicts on the heartbeat channel
DescriptionMy setup: One server with two nodes: oracle source (called oracle) and target mysql (called mytest).

I was playing around with MONITOR and NOTIFICATION tables:

* I got some other batches in error at this point and I wanted to receive a notification.
* I have inserted the attached rows into oracle (I didn't insert anything to MONITOR_EVENT, and I didn't touch SYM_* tables in MySQL database).
* The server tried to send the notification properly.
* I have marked the ER batch as OK (to stop the notifications).
* I went to sleep, with server still running. In the morning I was these in the logs.
* It seems that there are some other heartbeat batches with OK status and SQL_MESSAGE set as below (0000647:0000010% of all heartbeat batches logged through the night).
* Other than that, everything seems to be working correctly.

[mytest] - DataLoaderService - Failed to load batch oracle-2398
org.jumpmind.symmetric.io.data.writer.ConflictException: Detected conflict while executing UPDATE on wrygiel_usosweb.sym_monitor_event. The primary key data was: {monitor_id=error_detector, node_id=oracle, event_time=2016-09-22 07:13:00.013000000}. Failed to fallback. The original error message was: Duplicate entry 'error_detector-oracle-2016-09-22 07:13:00' for key 'PRIMARY'
        at org.jumpmind.symmetric.io.data.writer.AbstractDatabaseWriterConflictResolver.performFallbackToUpdate(AbstractDatabaseWriterConflictResolver.java:238)
        at org.jumpmind.symmetric.io.data.writer.DefaultTransformWriterConflictResolver.performFallbackToUpdate(DefaultTransformWriterConflictResolver.java:110)
        at org.jumpmind.symmetric.io.data.writer.AbstractDatabaseWriterConflictResolver.needsResolved(AbstractDatabaseWriterConflictResolver.java:92)
        at org.jumpmind.symmetric.io.data.writer.AbstractDatabaseWriter.write(AbstractDatabaseWriter.java:175)
        at org.jumpmind.symmetric.io.data.writer.NestedDataWriter.write(NestedDataWriter.java:64)
        at org.jumpmind.symmetric.model.ProcessInfoDataWriter.write(ProcessInfoDataWriter.java:65)
        at org.jumpmind.symmetric.io.data.writer.NestedDataWriter.write(NestedDataWriter.java:64)
        at org.jumpmind.symmetric.io.data.writer.TransformWriter.write(TransformWriter.java:207)
        at org.jumpmind.symmetric.io.data.DataProcessor.forEachDataInTable(DataProcessor.java:200)
        at org.jumpmind.symmetric.io.data.DataProcessor.forEachTableInBatch(DataProcessor.java:170)
        at org.jumpmind.symmetric.io.data.DataProcessor.process(DataProcessor.java:116)
        at org.jumpmind.symmetric.service.impl.DataLoaderService$LoadIntoDatabaseOnArrivalListener$1.call(DataLoaderService.java:929)
        at org.jumpmind.symmetric.service.impl.DataLoaderService$LoadIntoDatabaseOnArrivalListener$1.call(DataLoaderService.java:915)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
[oracle] - AcknowledgeService - The outgoing batch mytest-2398 failed: . Detected conflict while executing UPDATE on wrygiel_usosweb.sym_monitor_event. The primary key data was: {monitor_id=error_detector, node_id=oracle, event_time=2016-09-22 07:13:00.013000000}. Failed to fallback. The original error message was: Duplicate entry 'error_detector-oracle-2016-09-22 07:13:00' for key 'PRIMARY'
[mytest] - PullService - There was a failure while pulling data from oracle:oracle:oracle on channel thread default. 2 rows and 1 batches were processed

TagsNo tags attached.

Relationships

related to 0002788 closedelong Sync of monitor events gets unique key violation 

Activities

wrygiel

2016-09-22 07:52

reporter  

2016-09-22 09_38_06-C__Users_wrygiel_Desktop_screenshots.png (82,918 bytes)   
2016-09-22 09_38_06-C__Users_wrygiel_Desktop_screenshots.png (82,918 bytes)   

wrygiel

2016-09-22 07:53

reporter  

2016-09-22 09_52_51-Oracle SQL Developer _ Table SYMMETRIC.SYM_OUTGOING_BATCH@WR.png (82,129 bytes)   
2016-09-22 09_52_51-Oracle SQL Developer _ Table SYMMETRIC.SYM_OUTGOING_BATCH@WR.png (82,129 bytes)   

wrygiel

2016-09-22 07:57

reporter   ~0000856

Note: I'm new to SymmetricDS. Perhaps having such conflicts is OK and they should be ignored? If so, then I will not report any more conflicts on system tables in the future.

elong

2016-09-22 11:36

developer   ~0000857

You should not get conflicts on heartbeat channel. It is a bug that is fixed by issue 2788 in version 3.8.4.

wrygiel

2016-09-22 11:39

reporter   ~0000858

Sorry, I will upgrade to 3.8.4 now. I believe that this issue can be closed then.

elong

2016-09-22 11:43

developer   ~0000859

Closing this issue. Let us know if you have any trouble with 3.8.4.

Issue History

Date Modified Username Field Change
2016-09-22 07:52 wrygiel New Issue
2016-09-22 07:52 wrygiel File Added: 2016-09-22 09_38_06-C__Users_wrygiel_Desktop_screenshots.png
2016-09-22 07:53 wrygiel File Added: 2016-09-22 09_52_51-Oracle SQL Developer _ Table SYMMETRIC.SYM_OUTGOING_BATCH@WR.png
2016-09-22 07:57 wrygiel Note Added: 0000856
2016-09-22 11:36 elong Note Added: 0000857
2016-09-22 11:36 elong Relationship added related to 0002788
2016-09-22 11:37 elong Status new => feedback
2016-09-22 11:39 wrygiel Note Added: 0000858
2016-09-22 11:39 wrygiel Status feedback => new
2016-09-22 11:43 elong Note Added: 0000859
2016-09-22 11:43 elong Status new => closed
2016-09-22 11:43 elong Resolution open => duplicate