Suggestion: Documentation Update for Clarification on Ports

[michaelmyc]

I was following the "multi-node multi-drive" instructions to set up a testing cluster and was struggling to get it running. Eventually I realized that since I was not using the default port, thus minio isn't binding to the port I'm using, thus not allowing connections in the cluster.

I think this should be included in the documentation as it's a huge gotcha that doesn't have clear error messages. It might also be good to update the single node versions as well as I think changing ports is something that's super common.

[ravindk89]

@michaelmyc can you provide us with more detail here?

https://min.io/docs/minio/linux/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html#create-the-service-environment-file

As per our docs, all nodes must use the same config - including MINIO_VOLUMES, which is where the listen port gets specified.

Eventually I realized that since I was not using the default port, thus minio isn't binding to the port I'm using, thus not allowing connections in the cluster.

How were you specifying a non-default port here? Can you provide some specific examples?

[michaelmyc]

Sorry for the late reply.

The listening ports I was referring to is "--address" in "MINIO_OPTS".

The config is the same for all nodes, it's just that in MINIO_VOLUMES, I set the port to something other than 9000, and I can't get the cluster working without adding the "address" option in MINIO_OPTS. It's something that's really easy to miss and I only figured it out by thoroughly reading through the manual.

[ravindk89]

Hm. Interesting.

@harshavardhana @kannappanr arguably if I set

MINIO_VOLUMES=https://minio-{1...n}.example.net:9090/mnt/disk{1...n}

We should parse and use the :9090 and override the default value or that specified to --address. It would be odd to require it in both places, unless it's prohibitively complex to infer it from the VOLUMES.

[ravindk89]

@michaelmyc can you confirm the error you got when setting just MINIO_VOLUMES ? And what MinIO version you are running here.

[michaelmyc]

Our group is already using the deployment, so unfortunately it's not that convenient for me to take down the cluster and restart it.

If I recall correctly, the only error I saw was that minio complaining that the other node wasn't available. I remembered it was confusing and I got stuck on it for quite a while before I saw another config by one of my colleagues when he tested a single-node setup and realized I needed to add the --address option.

[ravindk89]

Thanks - that's enough for me to work with. I'm going to test a few scenarios and see what's happening here.