Non-BDA Nodes which are Part of a BDA Cluster Require Sufficient Space in /opt/cloudera/parcels Before Mammoth Upgrade
(Doc ID 2403960.1)
Last updated on MAY 29, 2018
Applies to:Big Data Appliance Integrated Software - Version 4.8.0 and later
Non-BDA nodes which are part of a BDA cluster require approximately 6 GB of free space in /opt/cloudera/parcels in order for Mammoth upgrade to successfully activate the new CDH parcels to these nodes. If sufficient storage does not exist in /opt/cloudera/parcels on the non-BDA nodes, Mammoth upgrade will fail when activating the new CDH parcels.
Follow the steps here to ensure that sufficient space exists in /opt/cloudera/parcels on non-BDA nodes which are part of the cluster. The steps should be followed proactively to avoid Mammoth upgrade errors when activating the parcels on the non-BDA nodes. However if necessary they can be followed reactively during upgrade if Mammoth fails during parcel activation to the non-BDA nodes as described in: 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).
Anyone planning for or doing a Mammoth upgrade.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Prerequisite Steps to Determine Space Usage in /opt/cloudera/parcels|
|Steps to Clear Up Space in /opt/cloudera/parcels|