Cloudera Docs

Known Issues in Cloud Connectors

Learn about the known issues in Cloud Connectors, the impact or changes to the functionality, and the workaround.

Known Issues identified in Cloudera Runtime 7.3.1.1100 SP3 CHF 6

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.1000 SP3 CHF 5

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.900 SP3 CHF 4

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.706 SP3 CHF 2

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.600 SP3 CHF 1

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.500 SP3

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.400 SP2

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.300 SP1 CHF 1

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.200 SP1

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.100 CHF 1

There are no new known issues identified in this release.

Cloudera Runtime 7.3.1

AWS SDK 2.25.53 warning about transfer manager not using CRT client
7.3.1.0
Due to the AWS SDK 2.25.53 upgrade, the following warning might be seen:
5645:2024-09-13 16:29:17,375 [setup] WARN  s3.S3TransferManager
          (LoggerAdapter.java:warn(225)) - The provided S3AsyncClient is an instance of
          MultipartS3AsyncClient, and thus multipart download feature is not enabled. To benefit
          from all features, consider using S3AsyncClient.crtBuilder().build() instead
This error message is completely harmless and should be ignored. For more information, see HADOOP-19272.
None
CDPD-76378 Uploading files to S3 takes longer than expected
7.2.17 and its service packs, 7.2.18 and its service packs, 7.3.1.0
7.3.1.100
Uploading files to S3 on long haul networks is delayed if the file is smaller than 64MB. As the 100-continue header is not received immediately, the files are uploaded only after several retries. The delay in uploading is caused by the fs.s3a.connection.expect.continue S3A configuration parameter. The fs.s3a.connection.expect.continue S3A configuration property controls whether or not a PUT request to the S3 store sets the "Expect: 100-continue" header, and awaits a 100 CONTINUE response before uploading any data. This allows throttling and other transient problems to be reported by the S3 store before there is an attempt by the client to upload any data.

By default, the value of the configuration property is set to true, which means that the header is set, and a 100 CONTINUE response is required.

If there is a significant delay in uploading files or if the write time of jobs increases, you can set the fs.s3a.connection.expect.continue configuration property for your service to false.