ETag change reported by S3 while reading at position

1

Anyone here ever seen these types of errors before:

Error parsing JSON - re-open 's3a://bucket-name/object/key/path/1594252800.json': ETag change reported by S3 while reading at position 45583977. Version E9FD7F9FABE88B6ABDB3195DAA41B290 was unavailable

I get this on seemingly random files when Dremio is reading from an S3-like object store service. It’s causing queries and reflection refreshes to fail.

These JSON files are around 200-300 MB in size. It’s almost like it’s saying that the file has been modified while Dremio was still reading it, but I know this is not the case.

Dremio Build: 4.2.1-202004111451200819-0c3ecaea

2

Are you using encryption, SSL or KMS to manage encryption on the S3 bucket, and on the source to the json? Maybe if AWS rotated the key after position 45583977 was written then it could cause a midfile problem? If it used the same key to write as it did to read then maybe that could fix it.

3

No encryption, SSL or KMS in this case.