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

TCP input message size problem, maybe a bug #11966

Closed
jiayuchen opened this issue Apr 27, 2019 · 0 comments · Fixed by #12385
Closed

TCP input message size problem, maybe a bug #11966

jiayuchen opened this issue Apr 27, 2019 · 0 comments · Fixed by #12385
Labels
bug Filebeat Filebeat good first issue Indicates a good issue for first-time contributors

Comments

@jiayuchen
Copy link

When Filebeat uses TCP input, we can set the option max_message_size as maximum size in bytes of the message received over TCP. But, there is another option that limits the message size when Filebeat calls

scanner.Scan()

to collect data: MaxScanTokenSize, the meaning of this option is the maximum size used to buffer a message. Filebeat does not override MaxScanTokenSize with max_message_size, which causes an error when the value of max_message_size we set is greater than MaxScanTokenSize and the length of our message is greater than MaxScanTokenSize and less than max_message_size. (position: filebeat/inputsource/tcp) . beats version: 6.5.4, but 7.0 also has this problem.

@urso urso added bug Filebeat Filebeat good first issue Indicates a good issue for first-time contributors labels Apr 29, 2019
kvch pushed a commit that referenced this issue Jun 28, 2019
Scanner buffer size is set to `maxMessageSize`

Fixes #11966
kvch added a commit to kvch/beats that referenced this issue Jun 28, 2019
kvch added a commit that referenced this issue Jul 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Filebeat Filebeat good first issue Indicates a good issue for first-time contributors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants