You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure whether this is an actual death or a really long wait or some dropped conn and no message/recovery. However, when testing the parsing pr #7057 I had to run/delete/run this harvest several times. Normally it completes in just a few minutes but a few times it just stopped logging those annoying citation date warnings for every dataset and then nothing for at least a half hour. This is long enough to appear to me that something is hung up or halted but no error in server log or harvest log. It happened often enough to report this as an issue. Maybe needs some better error handling in some special circumstance?
To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'.
If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment.
I'm not sure whether this is an actual death or a really long wait or some dropped conn and no message/recovery. However, when testing the parsing pr #7057 I had to run/delete/run this harvest several times. Normally it completes in just a few minutes but a few times it just stopped logging those annoying citation date warnings for every dataset and then nothing for at least a half hour. This is long enough to appear to me that something is hung up or halted but no error in server log or harvest log. It happened often enough to report this as an issue. Maybe needs some better error handling in some special circumstance?
Update: turns out this did not actually fail but waiting for 15mins to continue. Might still be worth looking into. There is also this diagnostic feature of payara I'd come across that may help? https://blog.payara.fish/introducing-the-stuck-threads-healthcheck-in-payara-server-173
The text was updated successfully, but these errors were encountered: