-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
DorisExporter marshal all data to single json array lead to stream load request too small #36896
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Thanks for your advice, I will change it with the first method you mentioned. |
By the way, another reason for too many requests might be that you don't have a batch processor in the config file. |
I had added batch processor and caught error said my data size exceed |
) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Send json lines to doris rather than json array. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #36896 <!--Describe what testing was performed and which tests were added.--> #### Testing unit test <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
Component(s)
exporter/doris
Describe the issue you're reporting
DorisExporter use stream load to insert data into doris. stream load have a default load limitation
streaming_load_max_mb
(default 10GB), but currently DorisExporter marshal all data to a single json array so request size restricted bystreaming_load_json_max_mb
(default only 100MB) so the maximum request body size each stream load request DorisExporter send is only 100MB. As a result, otel collector have to send too many small requests to doris, it's very ineffective.I hope DorisExporter could reduce write requests frequency to doris. I think implementation below maybe feasible:
streaming_load_json_max_mb
The text was updated successfully, but these errors were encountered: