shaofengshi commented on issue #6156: URL: https://github.com/apache/gravitino/issues/6156#issuecomment-3573656289
I also encountered the timeout issue when creating a fileset with Minio service running in Docker. Finally I verified that: 1) using both IP address and container name are working; 2) without adding "gravitino.bypass.fs.s3a.path.style.access=true" into the catalogs/hadoop/conf/hadoop.conf (Gravitino 0.9 or lower version) or catalogs/fileset/conf/fileset.conf (Gravitino v1.0 or higher version), the fileset creating request with a s3 location to Minio will be hung up until timeout. 3) Setting "gravitino.bypass.fs.s3a.path.style.access=true" in the fileset catalog properties couldn't work. 4) after adding "gravitino.bypass.fs.s3a.path.style.access=true" to catalogs/fileset/conf/fileset.conf (my version is 1.0), and then restart Gravitino service, the fileset creating is working. So, the conclusion from me is, the "gravitino.bypass.fs.s3a.path.style.access=true" is a MUST for accessing a MinIO service. We need put it into document. Thanks for @gesaleh and @epilif1017a 's information, save me the day. -- 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]
