Known Issues in Cloud Connectors
Learn about the known issues in Cloud Connectors, the impact or changes to the functionality, and the workaround.
- CDPD-48113: The option key to enable/disable readahead on the ABFS connector is changed to fs.azure.enable.readahead.v2 It is enabled by default, so read-ahead is active even if fs.azure.enable.readahead is false. This ensures that readahead is automatically re-enabled on releases where the HADOOP-18521 is fixed.
- None
- CDPD-46175: HADOOP-18521. ABFS prefetching input stream corruption
- set fs.azure.enable.readahead to false
- OPSAPS-72509, CDPD-32440: Hive metadata transfer to GCS fails with ClassNotFoundException
-
Hive replication policies from an on-premises cluster to cloud fails during the “Transfer Metadata Files” step if the following conditions are true:
- the target is a GCS Data Lake
- the source Cloudera Manager version is 7.11.3 CHF7, 7.11.3 CHF8, 7.11.3 CHF9, 7.11.3 CHF9.1, 7.11.3 CHF10, or 7.11.3 CHF11
fs.gs.delegation.token.binding
property is already defined in the configuration and cannot be unset to disable the delegation tokens in the cloud connector service. - CDPD-76378 Uploading files to S3 takes longer than expected
- 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 thefs.s3a.connection.expect.continue
S3A configuration parameter. Thefs.s3a.connection.expect.continue
S3A configuration property controls whether or not aPUT
request to the S3 store sets the"Expect: 100-continue"
header, and awaits a100 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 a100 CONTINUE
response is required.