View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006810 | SymmetricDS Pro | Bug | public | 2025-04-09 12:57 | 2025-04-09 12:57 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.16.0 | ||||
| Target Version | 3.16.2 | Fixed in Version | 3.16.2 | ||
| Summary | 0006810: If no threads available, compare requests can cause multiple compare statuses to process in loop | ||||
| Description | If no threads available in pool (or if the thread pool size is miscalculated) and user submits multiple compare requests at same time, it can cause the service to process the request multiple times, creating new compare IDs and compare status entries each time the job runs. - When multiple requests exceed available threads, gets stuck in loop processing requests - Processes requests even when no available threads - If no heartbeats recorded for cluster, mis-calculates number of available threads - Underestimates thread demand on a cluster | ||||
| Tags | compare repair | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-04-09 12:57 | elong | New Issue | |
| 2025-04-09 12:57 | elong | Status | new => assigned |
| 2025-04-09 12:57 | elong | Assigned To | => elong |
| 2025-04-09 12:57 | elong | Tag Attached: compare repair | |
| 2025-04-09 12:57 | elong | Issue generated from: 0006809 | |
| 2025-04-09 12:57 | elong | Relationship added | related to 0006809 |
| 2025-04-09 12:57 | elong | Status | assigned => resolved |
| 2025-04-09 12:57 | elong | Resolution | open => fixed |
| 2025-04-09 12:57 | elong | Fixed in Version | => 3.16.2 |