View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004586 | SymmetricDS | Bug | public | 2020-10-15 01:50 | 2022-08-01 19:30 |
| Reporter | gwilmer | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | no change required | ||
| Product Version | 3.11.7 | ||||
| Summary | 0004586: When sym_table_reload_status has more unprocessed rows than initial.load.extract.thread.per.server.count, loads don't queue | ||||
| Description | When sym_table_reload_status has more unprocessed rows than initial.load.extract.thread.per.server.count, loads don't queue from sym_table_reload_request. [Edit] Chris said that setting start.initial.load.extract.job=false is needed to reproduce this. We'll give that a try. | ||||
| Tags | No tags attached. | ||||
|
|
This is working as designed. There is a warning in the log and on the screen when you have more loads requested than threads. It is more efficient to process a load to completion than to task switch across multiple loads. Customers were complaining that loads were too slow, but it was the multi-tasking that made it appear slow, so it was changed to dedicate threads to loads. If you want more initial loads in parallel, then increase the thread count. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-10-15 01:50 | gwilmer | New Issue | |
| 2020-10-15 12:22 | elong | Note Added: 0001808 | |
| 2020-10-15 12:22 | elong | Status | new => feedback |
| 2020-10-15 19:27 | elong | Description Updated | View Revisions |
| 2022-08-01 19:30 | elong | Assigned To | => elong |
| 2022-08-01 19:30 | elong | Status | feedback => closed |
| 2022-08-01 19:30 | elong | Resolution | open => no change required |