0004188: Cancelling the "parent" initial load while extract service is Stopped leads to bad state - SymmetricDS

Summary	0004188: Cancelling the "parent" initial load while extract service is Stopped leads to bad state

Revision	2019-12-06 17:29 by hanes
Description	There's some sort of timing issue / state issue with the extract service when one cancels the parent initial load of a load initiated for multiple nodes. The simplest way to recreate that I've found is: 1. Stop Initial Load Extract service 2. Queue up an "all node" (need 2 or more) initial load 3. Wait for loads to appear on the Load Data screen 4. Cancel the first (i.e, the parent) load 5. Wait, then start the Extract service. The remaining extracts in sym_extract_request are marked as "NE" and have parent Ids still, yet it won't extract the requests. Note that the parent extract requests are all marked as "OK" and have a parent id of 0 (as expected).

Revision	2019-12-06 17:26 by hanes
Description	There's some sort of timing issue / state issue with the extract service when one cancels the parent initial load of a load initiated for multiple nodes. The simplest way to recreate that I've found is: 1. Stop Initial Load Extract service 2. Queue up an "all node" (need 2 or more) initial load 3. Wait for loads to appear on the Load Data screen 4. Cancel the first (i.e, the parent) load 5. Wait, then start the Extract service. The remaining extracts in sym_extract_request are marked as "NE" and have parent Ids still, yet it won't extract the requests