View Revisions: Issue #6815
| Summary | 0006815: Detect transport issues during Compare & Repair and retry automatically | ||
|---|---|---|---|
| Revision | 2025-04-16 19:34 by pbelov | ||
| Description | Currently the CompareService marks table-level step as failed, when one database endpoint is significantly slower than the other and table-level status does not match. When a faster node attempts to push checksum data to the slower node, their status codes do not match causing a rejected call and a prematurely closed HTTP connection. The CompareService.handlePutCompare method reports error: "Not ready to handle PUT for SQL08_Trigger-49-884 because level R does not match requested level F" Consider improving the CompareTransportManager.transportPushResource |
||
| Revision | 2025-04-10 15:16 by pbelov | ||
| Description | Currently the CompareService fails to process a table-level step, when one database endpoint is significantly slower than the other. When faster node attempts to push data to the slower node, their status codes do not match causing a rejected call and closed connection. The CompareService.handlePutCompare method reports error: "Not ready to handle PUT for SQL08_Trigger-49-884 because level R does not match requested level F" Consider improving the CompareTransportManager.transportPushResource |
||