Use 24.3 and 17.2.7 ceph clusters to configure distributed storage . Service: Amazon S3; Status Code: 400; Error Code: XAmzContentSHA256Mismatch

Use 24.3 CE and 17.2.7 ceph clusters to configure distributed storage, an error message is reported when you start the cluster and quit in error. I’m sure the configuration of the s3 is correct.

org.apache.hadoop.fs.s3a.AWSBadRequestException: PUT 0-byte object  on dist/uploads: null (Service: Amazon S3; Status Code: 400; Error Code: XAmzContentSHA256Mismatch; Request ID: tx0000068258129cbf14590-00658a7371-76ebb-xibahe; S3 Extended Request ID: 76ebb-xibahe-sjzx; Proxy: null), S3 Extended Request ID: 76ebb-xibahe-sjzx:XAmzContentSHA256Mismatch: null (Service: Amazon S3; Status Code: 400; Error Code: XAmzContentSHA256Mismatch; Request ID: tx0000068258129cbf14590-00658a7371-76ebb-xibahe; S3 Extended Request ID: 76ebb-xibahe-sjzx; Proxy: null)
        at org.apache.hadoop.fs.s3a.S3AUtils.translateException(
        at org.apache.hadoop.fs.s3a.Invoker.once(
        at org.apache.hadoop.fs.s3a.Invoker.lambda$retry$4(
        at org.apache.hadoop.fs.s3a.Invoker.retryUntranslated(
        at org.apache.hadoop.fs.s3a.Invoker.retry(
        at org.apache.hadoop.fs.s3a.Invoker.retry(
        at org.apache.hadoop.fs.s3a.S3AFileSystem.createEmptyObject(
        at org.apache.hadoop.fs.s3a.S3AFileSystem.access$1900(
        at org.apache.hadoop.fs.s3a.S3AFileSystem$MkdirOperationCallbacksImpl.createFakeDirectory(
        at org.apache.hadoop.fs.s3a.impl.MkdirOperation.execute(
        at org.apache.hadoop.fs.s3a.impl.MkdirOperation.execute(
        at org.apache.hadoop.fs.s3a.impl.ExecutingStoreOperation.apply(
        at org.apache.hadoop.fs.statistics.impl.IOStatisticsBinding.lambda$trackDurationOfOperation$5(
        at org.apache.hadoop.fs.statistics.impl.IOStatisticsBinding.trackDuration(
        at org.apache.hadoop.fs.s3a.S3AFileSystem.trackDurationAndSpan(
        at org.apache.hadoop.fs.s3a.S3AFileSystem.trackDurationAndSpan(
        at org.apache.hadoop.fs.s3a.S3AFileSystem.mkdirs(
        at com.dremio.plugins.util.ContainerFileSystem.mkdirs(
        at com.dremio.exec.hadoop.HadoopFileSystem.mkdirs(
        at com.dremio.dac.homefiles.HomeFileSystemStoragePlugin.start(
        at com.dremio.exec.catalog.ManagedStoragePlugin.lambda$newStartSupplier$2(
        at com.dremio.exec.catalog.ManagedStoragePlugin.lambda$nameSupplier$4(
        at com.dremio.exec.catalog.ManagedStoragePlugin.lambda$refreshState$8(
        at java.util.concurrent.CompletableFuture$
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$


The extended request ID would usually tell what the error means but only AWS support has the error descriptions. Can you check if you can write something from the Dremio coordinator and executor to the bucket defined in dist:/// location?

Also want to check if the syntax is right in dremio.conf, are you able to send that? You also need a core-site.xml with the entries in the document below, can you please make sure that nothing is missed?

@as10128 From the Dremio executor and coordinator, are you able to read/write into that bucket?

I am deleting your last update as it contains your access and secret keys

@balaji.ramaswamy Yes, it can be accessed.

@as10128 Sorry, one last thing. Are you able to send bucker policies?

I use Ceph Object Storage. I don’t have bucker policies configured, the user has full permissions by default. I use the s3cmd tool to look at the policy:

s3cmd info s3://bucket1

s3://bucket1/ (bucket):
   Location:  sjzx
   Payer:     BucketOwner
   Expiration Rule: none
   Policy:    none
   CORS:      none
   ACL:       superuser: FULL_CONTROL

@as10128 Is Ceph object storage consudered a S3 compatible storage

Yes. Provides object storage functionality with an interface that is compatible with a large subset of the Amazon S3 RESTful API.

@as10128 Can you please try adding the below and see if the connection works


@balaji.ramaswamy I followed the documentation configuration for “Configuring Dremio for Minio” and I have added this parameter.

@as10128 One last test if it is possible, does connecting to Minio or regular S3 work? This is just to narrow down if this is specific to CEPH

Also any luck getting the error description from AWS on what the extended request id is?

@balaji.ramaswamy Minio is normal. But I don’t have a minio cluster, just a test environment.

@as10128 Minio is also considered S3 compatible. Are you able to connect to any other S3 other than CEPH? If you do not have one, that is totally fine, was just checking