-
Notifications
You must be signed in to change notification settings - Fork 626
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
fetchMaxBytes #192
Comments
@mickhansen is this issue related to #181 ? |
@haio Not directly. I implemented what you suggested. I'm however seeing issues with fetchMaxBytes as described. |
it should because the size single message is bigger than 1024 * 90, so the consumer can't ever get a complete message. |
@haio That doesn't really correspond with the fact that it will fetch 150 mesages at |
@mickhansen that's interesting, I need to reproduce it. |
Just made a test, in my test |
And getting one message at the time? |
yeah, it should be one message one request. you can use |
Somewhat off this topic, when we mention that fetchMaxBytes: 1024 * 128 does it mean that we are telling the consumer to fetch 128 messages of length 1kb each??..or does it just mean that it will fetch 128kB of messages.... |
@ginokurian No, that tells the consumer to fetch 128KB in total, however many messages that might be |
I'm using HighLevelConsumer with
autoCommit: false
, for each message i'm pushing it into an internal queue so i can parse them serially and then comitting the offset after all messages are parsed.However i'm having an issue with fetchMaxBytes. If set to
fetchMaxBytes: 1024 * 128
it works but i get a queue of 150 messages.If i set fetchMaxBytes to something lower,
1024 * 64
or1024 * 90
i don't get any messages at all.Any help would be appreciated, ideally i'd like less messages at a time so i can get more often commits in case of errors.
The text was updated successfully, but these errors were encountered: