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

ID	Project	Category	View Status	Date Submitted	Last Update

0004188	SymmetricDS Pro	Bug	public	2019-12-06 17:26	2019-12-09 17:27

Reporter	hanes	Assigned To	elong
Priority	normal
Status	closed	Resolution	fixed
Product Version	3.11.1
Target Version	3.11.2	Fixed in Version	3.11.2

Summary	0004188: Cancelling the "parent" initial load while extract service is Stopped leads to bad state
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).
Tags	initial/partial load

Date Modified	Username	Field	Change
2019-12-06 17:26	hanes	New Issue
2019-12-06 17:26	hanes	Status	new => confirmed
2019-12-06 17:29	hanes	Description Updated	View Revisions
2019-12-06 17:35	hanes	Tag Attached: initial/partial load
2019-12-06 19:15	elong	Assigned To	=> elong
2019-12-06 19:15	elong	Status	confirmed => assigned
2019-12-06 19:17	elong	Note Added: 0001666
2019-12-06 19:17	elong	Status	assigned => resolved
2019-12-06 19:17	elong	Resolution	open => fixed
2019-12-06 19:17	elong	Fixed in Version	=> 3.11.2
2019-12-06 19:17	elong	Target Version	=> 3.11.2
2019-12-06 19:18	elong	Project	SymmetricDS => SymmetricDS Pro
2019-12-09 17:27	admin	Status	resolved => closed

elong 2019-12-06 19:17 developer ~0001666	Not sure of the best way to fix this, but I will fix it for the console for now, since the "cancel" you're performing is a multi-step operation it's doing for you. We probably need a "symadmin cancel-load 123" feature that does the same thing for OSS.