View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006131 | SymmetricDS | Improvement | public | 2023-11-28 20:29 | 2023-11-28 20:36 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.14.5 | ||||
| Target Version | 3.14.11 | Fixed in Version | 3.14.11 | ||
| Summary | 0006131: Too many "Expected but did not receive an ack for batch" | ||||
| Description | Some deployments receive too many log entries for "Expected but did not receive an ack for batch" because any exception, including network errors, is causing the logic to run that looks for missing acks due to batch corruption. It should only run the logic for a ProtocolException. Also, when a corrupt batch is detected on the receiving side, it immediately throws an exception, which prevents subsequent batches from being received. For example, server sends batches 1 through 10 to client, but batch 5 has corruption, so client immediately stops with only batches 1 through 4 and acknowledges them. The server logic removes batches 5 through 10 from staging, but only batch 5 needs to be removed. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-11-28 20:29 | elong | New Issue | |
| 2023-11-28 20:29 | elong | Status | new => assigned |
| 2023-11-28 20:29 | elong | Assigned To | => elong |
| 2023-11-28 20:29 | elong | Issue generated from: 0006130 | |
| 2023-11-28 20:29 | elong | Relationship added | related to 0006130 |
| 2023-11-28 20:35 | elong | Status | assigned => resolved |
| 2023-11-28 20:35 | elong | Resolution | open => fixed |
| 2023-11-28 20:35 | elong | Fixed in Version | => 3.14.11 |
| 2023-11-28 20:35 | elong | Target Version | => 3.14.11 |
| 2023-11-28 20:35 | elong | Relationship added | related to 0005692 |
| 2023-11-28 20:36 | elong | Issue cloned: 0006132 | |
| 2023-11-28 20:36 | elong | Relationship added | related to 0006132 |
| 2023-12-16 01:56 | admin | Status | resolved => closed |