You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on those reports circa 2023, HAProxy has some fundamental incompatibility w/ certain MinIO S3 protocols around Tiering. At least one other user reported general slowness or other issues w/ HAProxy.
The ticket does have an example of an HAProxy config we could start with and experiment to see if we could resolve both the performance and S3 API issues. The latter is, according to a maintainer, not going away due to S3's implementation not respecting HTTP1/1 or something along those lines.
I think we have had customers and users on HAProxy before, but given the mixed results and compat concerns, we should drop it from docs until we have a formally reviewed and tested setup where all APIs are known to work and have normal/expected performance.
The text was updated successfully, but these errors were encountered:
@pavelanni I think in your example you set it to 1gi, but is there some other value here that makes sense? Body size shouldn't generally exceed the max part size + some buffer anyways right?
haproxy/haproxy#2076
Based on those reports circa 2023, HAProxy has some fundamental incompatibility w/ certain MinIO S3 protocols around Tiering. At least one other user reported general slowness or other issues w/ HAProxy.
The ticket does have an example of an HAProxy config we could start with and experiment to see if we could resolve both the performance and S3 API issues. The latter is, according to a maintainer, not going away due to S3's implementation not respecting HTTP1/1 or something along those lines.
I think we have had customers and users on HAProxy before, but given the mixed results and compat concerns, we should drop it from docs until we have a formally reviewed and tested setup where all APIs are known to work and have normal/expected performance.
The text was updated successfully, but these errors were encountered: