View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005858 | SymmetricDS | Bug | public | 2023-05-23 15:00 | 2024-06-19 17:45 |
| Reporter | emiller | Assigned To | |||
| Priority | normal | ||||
| Status | new | Resolution | open | ||
| Product Version | 3.14.0 | ||||
| Summary | 0005858: Row in sym_table_reload_status does not get its setup_batch_loaded column updated appropriately | ||||
| Description | It's possible for a sym_table_reload_status entry to not get its setup_batch_loaded column updated when batches are loaded. As a result, the row gets stuck in a state where end_time=null and completed=0. In the pro UI, the load gets stuck in the "Loading" state with no additional progress being made. When this issue occurs, most loads are successful and the issue only affects a small number of them. It is expected to be a timing issue. In one instance, this issue occurred when sending multiple loads for individual tables with sym_table_reload_request.delete_first=1. In this case, the source node was extract only and the target node was load only. Unlike issue 0005651, the datareload.batch.insert.transactional parameter was set to its default value of true. It's possible that in order to reproduce this, the source and target databases would have to be slow. | ||||
| Tags | No tags attached. | ||||
|
|
The following log message was added in AcknowledgeService when a duplicate load status update gets ignored: log.info("Ignoring duplicate load status update for load ID {} with batch {}", outgoingBatch.getLoadId(), outgoingBatch.getNodeBatchId()); |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-05-23 15:00 | emiller | New Issue | |
| 2023-05-23 15:00 | emiller | Relationship added | related to 0005315 |
| 2023-05-23 15:00 | emiller | Relationship added | related to 0005651 |
| 2024-06-19 17:44 | emiller | Note Added: 0002465 | |
| 2024-06-19 17:45 | emiller | Note Edited: 0002465 | View Revisions |