My Oracle Support Banner

Mammoth Upgrade Fails at Step 5 when Distributing Parcels Due to Insufficient Space in /opt/cloudera/parcels on Non-BDA Cluster Nodes (Doc ID 2401493.1)

Last updated on MAY 28, 2018

Applies to:

Big Data Appliance Integrated Software - Version 4.8.0 and later
Linux x86-64

Symptoms

1. Mammoth upgrade fails at Step 5 when distributing parcels with an error like below.

Error [17516]: (//bdanode01.example.com//Stage[main]/Hadoop::Upgradecdh/Exec[upgrade_cdh]/returns) change from notrun to 0 failed: /opt/oracle/BDAMammoth/bdaconfig/tmp/upgradecdhparcel.sh &> /opt/oracle/BDAMammoth/bdaconfig/tmp/upgradecdhparcel.out returned 1 instead of one of [0]

2. Navigating in Cloudera Manager:  Hosts > Parcels shows that the parcels for the release being upgraded to are being "Activated" but that activation fails due to lack of space on one of the non-BDA edge nodes preventing parcel distribution there. For example for an upgrade to BDA V4.11, CDH 5.13.1 an error is raised in Hosts > Parcels when "Activating" the parcel 5.13.1 being upgraded to. 

a) The error looks like: 

                            5.13.1-1.cdh5.13.1.p0.2

                                                                                     Activating 91%  Details

  • Error when distributing to <edgenodehost1>.example.com.  [Errno 28] No space left on device.
  • Error when distributing to <edgenodehost2>.example.com.  [Errno 28] No space left on device.

 

b) Navigating in CM: Hosts > Parcels shows:

 

3. Monitoring Hosts > Parcels shows that the error intermittently switches over to a "Checksum mismatch" error for the non-BDA hosts.  This error is raised because the parcel can not be properly activated resulting in a checksum mismatch from the expected parcel.

a) The error looks like:

                           5.13.1-1.cdh5.13.1.p0.2

                                                                                    Activating 91% Details

  • Error when distributing to <edgenodehost1>.example.com. Checksum mismatch.
  • Error when distributing to <edgenodehost2>.example.com. Checksum mismatch.

b) Navigating in CM: Hosts > Parcels shows:

 

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.