xiacongling opened a new issue, #59781:
URL: https://github.com/apache/doris/issues/59781

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Version
   
   3.1.4
   
   ### What's Wrong?
   
   We encountered an stream load error for wide tables after upgrading our 
cluster to version 3.1.4:
   
   ```
   org.apache.doris.spark.exception.StreamLoadException: stream load failed, 
status: 431, reason: Request Header Fields Too Large
   ```
   
   Even though changing FE config `jetty_server_max_http_header_size` to an 
extremely large number (such as 1048576 for 1MB header), the problem still 
exists.
   
   We found that the properties for configuring jetty server in 
`org.apache.doris.httpv2.HttpServer` are out-dated after spring boot 2.3 been 
released.
   
   
https://github.com/apache/doris/blob/6384827648b7cfbea53b4257a9407ae118441213/fe/fe-core/src/main/java/org/apache/doris/httpv2/HttpServer.java#L160-L169
   
   ref: 
https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.3.0-M4-Configuration-Changelog
   
   ### What You Expected?
   
   update jetty property names to fix the problem
   
   ### How to Reproduce?
   
   stream load into wide tables whose column list is very long (max header size 
is 8k by default)
   
   ### Anything Else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to