How to stop a import process in background

I had to manually alter the feeds source table entry and change state to "b:0;". =/

Would appreciate a better solution, some imports are too big, and you want to start from scratch again.

Delete the relevant entry from the batch table? Works for non-background imports, you get an error in the browser as soon as the next refresh occurs.

Fonant, if something happens that break an ongoing batch process, then it falls back to background, that's the issue, at least it's what happens to me when going on non-background imports.

this maybe an easier solution
http://drupal.org/node/1030710#comment-5052738
but a cancel button would be nice

Thanks Franz, setting the state to "b:0;" seems to have worked for me.
I couldn't rename any files (GiorgosK's solution) since the source was a database - which I didn't want to take down just to trigger an error ;)

Actually, it resumed, updating the state field. Then I noticed the "unlock" tab, and hopefully "unlocking the importer" has stopped the import.

EDIT: Gah! No, next time cron executed it started again... Hrmm.

EDIT: Unlocking, and then "quickly" starting a new import seemed to get things back to normal (I'd also turned off the background import feature in the mean time).

First unlock the import in the UI. Then in the database 'feeds_source:state' should be empty.
It could be that the now cancelled background-import is still queued. In the database check 'queue' and remove entries with name 'feeds_source_import'.

Now the background-import should be really cancelled. It won't start again when running cron.

https://www.drupal.org/node/2371253#comment-9397255

Maybe unlocking a feeds source should also take care for remove entries from the queue?

If it helps anyone:

1. Unlock the import between cron runs.
2. Delete the data file from the public folder (usually /sites/default/files/feeds/)

That seems to stop the import midway.
The unlocking step may not even be necessary.

The log entry simply says:

"File public://feeds/xyz.csv does not exist."

@serenity1
If I remember correctly, it is since Feeds 7.x-2.0-beta4 that removing the file that is in progress of being imported helps with stopping the import. Before, Feeds would just retry to continue the import on each cron run.
I could be wrong on this though, but I did make several improvements regarding scheduling imports like #2871580: Jobs for no longer existing feeds are kept being scheduled for example.

That's great, MegaChriz!
Just shared the steps in case it helps someone.

Also made a suggestion that might be an easy workaround for #1795262: Schedule import to run at specific times.
Please do take a look when you have the time.

Drupal 7 reached end of life and the D7 version of Feeds is no longer being developed. To keep the issue queue focused on supported versions, we’re closing older D7 issues.

If you still have questions about using Feeds on Drupal 7, feel free to ask. While we won’t fix D7 bugs anymore, we’re happy to offer guidance to help you move forward. You can do so by opening (or reopening) a D7 issue, or by reaching out in the #feeds channel on Drupal Slack.

If this issue is still relevant for Drupal 10+, please open a follow-up issue or merge request with proposed changes. Contributions are always welcome!