About shubham_rai

shubham_rai · ‎12-17-2025

We recently performed a cluster-level rolling upgrade using Cloudera Manager (CDP Private Cloud Base 7.1.9) on our High Availability (HA) enabled cluster. During the rolling restart phase, we selected: * All services (including Hive-on-Tez) * All roles (including non-worker roles) * Restart roles with stale configurations only * Restart roles with old software versions only * Redeploy client configuration Despite these selections, the Hive-on-Tez service (specifically the HiveServer2 role) was not restarted. Post-upgrade, HiveServer2 continues to show a stale configuration warning in Cloudera Manager. This behavior suggests that HiveServer2 was skipped during the rolling restart, even though it should have been included based on the selected options. We would appreciate your assistance in: 1. Confirming whether this is expected behavior or a known issue. 2. Advising on the correct procedure to ensure Hive-on-Tez roles are properly restarted during rolling upgrades. 3. Recommending any patches or configuration changes to prevent this in future upgrades. Please let us know if any additional logs or diagnostic information are needed.

shubham_rai · ‎09-09-2025

Hi @DianaTorres, Thanks for your reply. I resolved this issue by modifying the networking. Best regards, Shubham Rai.

shubham_rai · ‎09-09-2025

We have seen that a CDP AWS Datahub cluster was created but failed shortly after due to the master node becoming unreachable, resulting in errors like: 1) Cluster creation timeout 2) Unreachability 3) Abrupt failure due to unhealthy nodes We have seen that our custom service "MY_SERVICE" was ruled out based on cluster logs and suspect network or connectivity issues. We have also observed: The Cloudera Manager instance in our CDP AWS Datahub environment is currently marked as unhealthy and is not responding. AWS diagnostics show that the instance status check has failed at the OS level, indicating a deeper issue with the instance configuration itself.

shubham_rai · ‎08-05-2025

Hi @DianaTorres @PabitraDas @zzeng @venkatsambath, I hope you guys are doing well. I'm currently working on CDP AWS Datahub, and I’d appreciate your suggestions or insights, especially around the above issue I have mentioned. If you’ve encountered similar scenarios or have any recommendations, please feel free to share. Your input would be incredibly helpful. Thanks in advance! Best regards, Shubham Rai

shubham_rai · ‎07-31-2025

Environment: - CDP Public Cloud (AWS) - DataHub cluster with CDH 7.3.1 - Custom service: 'Service_Name' - Deployment via cluster template + pre/post recipes Problem: Cluster creation fails with the error: ``` No service type 'Service_Name' available for cluster with version 'CDH 7.3.1' ``` What we have done: - Created a valid 'Service_Name.jar' with: - 'descriptor/service.sdl' - 'cloudera-service.json' (includes '"cdhVersion": { "min": "7.3.1"}') - Used **pre-recipe** to download and place CSD and parcel files in '/opt/cloudera/csd/' and '/opt/cloudera/parcel-repo/' - Used **post-recipe** to distribute and activate parcels via Cloudera Manager API - Verified JAR contents and permissions - Still getting the same error during cluster creation ERROR: Installation of CDP with Cloudera Manager has failed. Please find more details on Cloudera Manager UI. Failed command(s): ClusterTemplateImport(id=1546337329): java.lang.IllegalArgumentException: No service type 'Service_Name' available for cluster with version 'CDH 7.3.1'. If you are attempting to add a service required for Cluster Upgrade, please specify the target version of your upgrade in the serviceVersion field Questions: 1. Is there any additional metadata or structure required in the CSD JAR for CDP AWS DataHub? 2. Does the service need to be pre-baked into a custom image for DataHub to recognize it? 3. Are there any known limitations or timing issues with using recipes to deploy custom services in DataHub? Any guidance or examples from successful custom service deployments in DataHub would be appreciated!

shubham_rai · ‎04-22-2025

Hello All, We have created a custom parcel for Cloudera runtime version 7.1.8 with OS RHEL 7. Our cluster is now operating in mixed OS mode, with some nodes upgraded to RHEL 8 while others are still running on RHEL 7. After the upgrade, Cloudera Manager UI is showing an error for the parcel: "Parcel not available for OS distribution RHEL 7." Is there a way to create parcels for both OS versions so that they can be distributed in mixed OS mode? Thanks,

Online	Online
Last Visited	‎12-28-2025 09:03 PM

Member Since	‎04-22-2025 03:13 AM
Last Visited	‎12-28-2025 09:03 PM
Posts	6

Cloudera Community

Re: Custom Service Fails to Deploy in CDP DataHub ...

Hive-on-Tez Not Restarting During Cluster-Level Ro...

Re: Custom Service Fails to Deploy in CDP DataHub ...

CDP AWS Datahub cluster is not working as expected...

Re: Custom Service Fails to Deploy in CDP DataHub ...

Custom Service Fails to Deploy in CDP DataHub 7.3....

Issue with parcels distribution on mixed OS in CDP...