-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature request] stop an harvest job in progress #7940
Comments
Thanks @virgilejarrige, and good to see you at some #dataverse2021 sessions this week. I think it's a good idea to not have this be reliant on a DB update, but we should also examine and fix the failure cases that results in this condition in the first place as well. |
Hey Danny! We had two cases in which this happened: 1 - The harvest of an entire data repository (Nakala) - which worked but was so huge it made our postgresql bdd too big for the VM it was in. As it's on our "all-in-one" test server, we had to use a snapshot to restore it. 2 - The haverst of an ahp collection - which was ended with the DP Update and in the dashboard now we have "SUCCESS; 0 harvested, 0 deleted, 0 failed." |
sprint:
Desired behavior is to stop the harvesting that is in progress as opposed to a pause state.
|
Sprint
|
Sprint:
|
Waiting on PR8753 to clear. |
Is this issue in scope as well? |
(resolved merge conflict in HarvesterServiceBean.java) (also, it may be easier to abandon this branch and create one from scratch) (#7940)
Hello,
I ran into the issue described here: https://groups.google.com/g/dataverse-community/c/O-NdDtgFrI0/m/os_KjdLxAQAJ
The process worked, but maybe it would be a good idea to have a button that would do the same thing on the harvest page? or maybe an API to reset stuck harvest?
Here is what i've done:
#manually get the harvest job's id:
select * from harvestingclient;
#fix the issue - where {ID} is the database id of the harvesting client.
UPDATE clientharvestrun SET harvestresult=0 WHERE harvestingclient_id={ID} AND harvestresult = 2;
UPDATE harvestingclient SET harvestingnow = FALSE WHERE id={ID};
#restart payara "just in case"
systemctl restart payara
Take care,
Virgile
The text was updated successfully, but these errors were encountered: