-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Inconsistent results in pull queries with distributed KsqlDB setup #10241
Labels
Comments
Some addition. I tried to create a table with only one partition:
So there is only one partition but it still collects the keys from 0 to 59. And it's the same behavior. When I run pull query for 20 hours I expect to receive 1200 rows in results. Most times it is 1200 rows but from time to time it could be 1199, 936 or even 1201 rows! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Setup
First of all, we have 6 machines each containing its instance of running in Docker from the image
confluentinc/ksqldb-server v 0.29.0
.Second, we have this setup:
We have a scenario very similar to what is described here.
events
.It created for us 3 topics, 1 visible and 2 hidden.
The problem
When we issue pull queries for this table it returns us sporadically inconsistent results without any errors in logs.
Our queries look like this:
We run them against already closed periods so we expect that newly arrived data shouldn't interfere with it.
We expect to get data from 60 partitions per hour but sometimes (roughly 1 out of 10) it returns us fewer rows from 44 to 54 and sometimes even 61.
My guess is some of the nodes "timeout" and do not return results in our multi-node setup but without any errors in logs, it's hard to investigate further.
If anyone could help somehow or point to the direction where to dig it would be great. Thanks in advance!
The text was updated successfully, but these errors were encountered: