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

need a handler throttle #8

Open
richwolski opened this issue Aug 16, 2017 · 0 comments
Open

need a handler throttle #8

richwolski opened this issue Aug 16, 2017 · 0 comments
Assignees

Comments

@richwolski
Copy link
Contributor

woofc-container uses multiple threads to service the event log and (now) forks and execs each handler. If one handler does multiple puts, it is possible to create a backlog of processes within the container. Probably need a throttle that will restrict new process spawns when the backlog reaches a specified maximum. The easiest way to do this would be to add a global semaphore to woofc-container that the WooFForker() threads use to determine when it is safe to call fork()

@richwolski richwolski self-assigned this Aug 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant