Should we have to wait for completion of delete process before re-importing the data when there are thousands of row to be deleted.

Reason I am asking is when GUID is mapped to unique column value and setting like "update existing node" there is no option(or is it required?) like not to check for GUID for nodes which are being marked for deletion in cron.

Or re-importing will break the existing delete process job and perform import /update on those nodes?

Comments

nithinkolekar created an issue. See original summary.

twistor’s picture

twistor CreditAttribution: twistor as a volunteer commented
Category: Task » Support request
Status: Active » Fixed

You can only run one operation on a feed at a time. This is by design. Trying to delete entities while also trying to import them is too difficult to reason about.

There is no "marked for deletion" stage. If cron is deleting nodes, then you have to wait for that to finish before you can run the import again.

If you're running into issues where the feed is locked, I would recommend running cron more frequently. Or, even better, use drush queue-run to continually execute the queue that's holding things up.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.