Open christiandtk opened 10 months ago
We are thinking about the validation. However, it may not be proper to check on FE host, since FE won't connect to S3 for anything in shared-data mode for the storage volume. FE host has difficulty to connect to the S3 service, doesn't necessarily mean that BE will have the same issue. It is possible that the access policy limits to only BE hosts has access to the S3 service, that would be totally fine for current shared-data deployment.
We have marked this issue as stale because it has been inactive for 6 months. If this issue is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 10 days to keep the issue queue tidy. Thank you for your contribution to StarRocks!
Enhancement
I was using S3 in my FE conf. Instead of getting an error that StarRocks could not connect to S3 I was thrown a ton of random errors. I think a check for S3 connection with a clear error should be added.
S3 conf in fe.conf was using https when it should have been http. Not sure but I feel this should be checked when adding a storage volume and throw a "Could not connect to S3"