View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006207 | SymmetricDS | Bug | public | 2024-01-25 18:44 | 2024-02-15 20:28 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.15.0 | ||||
| Target Version | 3.15.3 | Fixed in Version | 3.15.3 | ||
| Summary | 0006207: Reverse initial load sometimes doesn't start when also using forward initial load | ||||
| Description | If parameters are set to initial load (auto.reload) and reverse initial load (auto.reload.reverse), sometimes the reverse initial load won't start. It sometimes happens if the initial load is started before batches containing the sym_table_reload_request can sync down to client. The initial load will mark outstanding batches as OK, but it should avoid doing that for config and monitor channels. (Currently sym_table_reload_request is placed on the monitor channel along with sym_table_reload_status to observe the progress of an incoming load.) | ||||
| Tags | initial/partial load | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-01-25 18:44 | elong | New Issue | |
| 2024-01-25 18:44 | elong | Status | new => assigned |
| 2024-01-25 18:44 | elong | Assigned To | => elong |
| 2024-01-25 18:44 | elong | Tag Attached: initial/partial load | |
| 2024-01-25 18:59 | elong | Status | assigned => resolved |
| 2024-01-25 18:59 | elong | Resolution | open => fixed |
| 2024-01-25 18:59 | elong | Fixed in Version | => 3.15.3 |
| 2024-02-05 18:58 | admin | Status | resolved => closed |
| 2024-02-15 20:28 | admin | Changeset attached | => SymmetricDS 3.15 b7399007 |