Skip to content
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

disabling harvesting schedule doesn't disable harvesting schedule #3985

Closed
donsizemore opened this issue Jul 7, 2017 · 2 comments
Closed

Comments

@donsizemore
Copy link
Contributor

donsizemore commented Jul 7, 2017

Tested on 4.5 and 4.7. Walk through admin dashboard wizard to edit harvesting client settings. Set schedule to "None" and save changes, but the schedule remains in place.

Setting harvestingclient.scheduled to 'f' and refreshing the page appears to disable it.

@djbrooke
Copy link
Contributor

djbrooke commented Jul 7, 2017

Thanks @donsizemore. We'll take a look.

@kcondon
Copy link
Contributor

kcondon commented Jul 26, 2017

Tested the fix and the UI state is now corrected due to this fix. However, there is an underlying timer and harvesting status issue that also needs to be addressed to make this work well -when the web server running the harvest is restarted, any current harvest job is halted. So, upon restart, any running harvest job needs to have the flag harvestingnow in the table harvestingclient set to 'f' . There also seems to be a proliferation of timer jobs in the EJB__TIMER__TBL which likely means they are not being cleaned up when deleted/disabled. This may need a separate ticket, will discuss in standup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants