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

itemsBeingProcessed is always 1 regardless of worker count #1165

Open
jfernandez opened this issue Sep 30, 2023 · 0 comments
Open

itemsBeingProcessed is always 1 regardless of worker count #1165

jfernandez opened this issue Sep 30, 2023 · 0 comments

Comments

@jfernandez
Copy link
Contributor

jfernandez commented Sep 30, 2023

At Netflix, we are running a custom fork with this change to expose the itemsBeingProcessed map size: #1162

We have implemented a gauge metric to monitor the size of itemsBeingProcessed at short intervals. Despite having a significant queue size and operating with 20 workers, the maximum value observed for this metric is 1, indicating only one item is being processed at a time, contrary to our expectation of parallel processing by multiple workers.

We suspect that the waitForNextItemSemaphore might be the cause of this serialization. Is this a possible explanation?

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