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.

Sign up for GitHub

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

Jump to bottom

ocrd network: proper timeouts for processing #1074

Open
bertsky opened this issue Jul 12, 2023 · 0 comments
Open

ocrd network: proper timeouts for processing #1074

bertsky opened this issue Jul 12, 2023 · 0 comments

Comments

@bertsky
Copy link
Collaborator

bertsky commented Jul 12, 2023

For running jobs, we agreed there is a need for some kind of timeout anyway, universally. It gets enforced by

  • Processor Server model: the calling Processing Server (currently with a dummy number of pages of 200) or client CLI
  • Processing Worker model: the worker instance (around invoke_processor()) or the processor itself (inside process())

Whoever witnessed a timeout must then either resubmit or roll back upstream, i.e. push back on the queue.

To calculate the number of pages in advance, see #1063

Originally posted by @bertsky in #1069 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bertsky