-
Notifications
You must be signed in to change notification settings - Fork 41
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
Account stream length lower bounded at ~250 entries #46
Comments
This comment was marked as spam.
This comment was marked as spam.
Hrm I havent seen this, perhaps this could it be a redis stream size is more of a estimate size? |
I've observed issues like this for both TXN and ACC stream and I believe its related to how we read from the Redis streams. We haven't gotten the chance yet to dive deeper and confirm though. |
I think we can close this as its now a config item |
can we close thid |
Hi @austbot I don't think this is the case. The redis queues don't empty out and it does not look like it's based on the batch sizes. It looks like somehow some parts of the queue never gets read? If you have some suggestions for how to validate this though I'm all ears. Maybe I could inspect the redis queue without processing it? I'll have to look up how to do that. |
Across our two envs we know have a baseline minimum of entries in the account stream. It keeps defaulting to having 218 and 243 entries in the account stream. These are two independent environments.
Adding this as a placeholder issue while we continue to investigate on our end.
The text was updated successfully, but these errors were encountered: