Add Documentation for Replication Using a Load Balancer #2375
+55
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cniackz
requested review from
vadmeste,
dvaldivia,
ramondeklein and
pjuarezd
vadmeste
reviewed
Dec 25, 2024
| @@ -131,3 +131,58 @@ spec: | |||
| port: | |||
| number: 9443 | |||
| ``` | |||
|
|
|||
| ### Replication configuration: | |||
There was a problem hiding this comment.
This is not necessarly related to replication, this is mainly a very slow deployment or best practice were not followed, like a user storing a lot of objects under a single prefix
the one here works most of the time,
https://min.io/docs/minio/linux/integrations/setup-nginx-proxy-with-minio.html
ravindk89
approved these changes
Dec 26, 2024
Comment on lines
+162
to
+163
| nginx.ingress.kubernetes.io/proxy-read-timeout: "60s" | ||
| nginx.ingress.kubernetes.io/proxy-send-timeout: "60s" |
There was a problem hiding this comment.
Q: Is there a value here we would consider to be too high? We have internal timeouts as well. Just curious.
|
|
||
| ### Replication configuration: | ||
|
|
||
| Sometimes, you need to configure timeout in order to avoid Load Balancer to kill the connection while replication is taking place, for that, we can configure a read/write timeout of X minutes in the provided load balancer, you can add the appropriate NGINX annotations to your ingress configuration under `metadata.annotations`. The relevant annotations are: |
There was a problem hiding this comment.
Rec based on Anis comment:
Suggested change
| Sometimes, you need to configure timeout in order to avoid Load Balancer to kill the connection while replication is taking place, for that, we can configure a read/write timeout of X minutes in the provided load balancer, you can add the appropriate NGINX annotations to your ingress configuration under `metadata.annotations`. The relevant annotations are: | |
| Ingress by default may time out connections before an operation completes. | |
| This is common with slower setups (network/drives) or poor operational practices (many objects in one prefix, flat organization). | |
| You can set a timeout value that is above what your cluster requires on average to complete an operation to address the above issue. | |
| Place the following nginx annotations in the ingress configuration under `metadata.anotations`: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Document a scenario where a load balancer terminates the connection during replication and provide guidance on how to resolve this issue.