View Issue Details

IDProjectCategoryView StatusLast Update
0004404SymmetricDSBugpublic2020-05-26 16:37
Reporterelong Assigned Toelong  
Status closedResolutionfixed 
Product Version3.11.0 
Target Version3.11.9Fixed in Version3.11.9 
Summary0004404: Initial load leaves batch in RQ status with message "batch not ready for delivery"
DescriptionWhen using initial load with extract job enabled, after re-installing a node and sending it an initial load, a batch can get stuck in the RQ status. From the logs, the batch is extracted to staging by the extract job, but the client cannot pull the batch because its status remains as RQ. In the database, the extract request is OK, but the outgoing batch status is RQ:

[server] Done with request 2 to extract table MYTEST into batches 9 through 9 for node 1
[server] Batch 9 is not ready for delivery. It is currently scheduled for extraction.

What's happening is the batch is already in staging, left over from a previous run with this node. When the extract job goes to extract the table, no data is processed because the batch is found in staging already, so the MultiBatchStaging writer is never called, and the batch status is never changed. The workaround is to remove staging files.
Tagsinitial/partial load


related to 0004398 closedelong Initial load leaves batch in RQ status with message "batch not ready for delivery" 


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2020-05-21 15:25 elong New Issue
2020-05-21 15:25 elong Status new => assigned
2020-05-21 15:25 elong Assigned To => elong
2020-05-21 15:25 elong Issue generated from: 0004398
2020-05-21 15:25 elong Relationship added related to 0004398
2020-05-21 15:25 elong Tag Attached: initial/partial load
2020-05-21 15:29 elong Status assigned => resolved
2020-05-21 15:29 elong Resolution open => fixed
2020-05-21 15:29 elong Fixed in Version => 3.11.9
2020-05-26 16:37 elong Status resolved => closed