-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
EnableIndexes is set to false but Index-related work are still being queued #1029
Comments
We meet a similar issue. {prefix}-index queue increased due to cannot consume in time and caused high server load of redis. |
@danielgerlag how about getting workflowoptions and disable queue and dequeue in redis queue provider? `
` |
Describe the bug
When EnableIndexes is set to false during set up, we are making IndexConsumer inactive. One issue is that QueueProvider.QueueWork(WorkflowId, QueueType.Index) is still being called in different places in the code, causing the queue for Index to build up.
To Reproduce
Steps to reproduce the behavior:
Set EnableIndexes to false and use Workflow Core. In Persistence of your choice (in my case Redis), you will see an entry for {prefix}-index. This persisted data will grow as there is no process dequeuing the entries
Expected behavior
When EnableIndexes is set to false, no queuing for QueueType.Index should happen.
Additional context
This behavior caused storage to increaase. In the case of Redis, Key with name {prefix}-index will keep growing in size as there is no process to dequeue the Index items.
The text was updated successfully, but these errors were encountered: