Applying a Patch for an Ecosystem Component
Patches for ecosystem components are handled differently from patches for Data Fabric core software.
About Patches for Ecosystem Components
Ecosystem components are updated as a package rather than a patch file. While core patches
typically include a prefix such as mapr-patch
or
mapr-patch-client
, ecosystem patches are delivered as a new package and
do not use the core patch mechanism.
To identify an ecosystem patch package, look for the component name in the patch name. For
example:
mapr-livy-0.7.0.304.202309110421-1.noarch.rpm
Then use the
steps on this page to update the currently installed package. The steps on this page use the
Livy component as an example.Downloading a Patch for an Ecosystem Component
Patches for ecosystem components can be downloaded from the secure FTP server. To download
a patch file for an ecosystem component:
- Use the steps in Downloading a Patch to sign in to the secure FTP server.
- Navigate to the
/ecosystem/rpm/<component-name>/
or/ecosystem/deb/<component-name>/
directory. - Click the patch to select it.
- Click Download.
Applying the Patch
To apply the patch:
- On all nodes where the ecosystem component is running, stop the service for the
component. For
example:
maprcli node services -name livy -action stop -nodes <ip_address>
- Before upgrading, check to see if other actions are needed. For example, you might want to back up configuration files for a component before upgrading. For more information, review the pre-upgrade steps for the component in Preparing to Upgrade the Ecosystem Pack.
- Use the following commands to upgrade the currently installed package for the
component. For example:
- On RHEL / CentOS or
SLES:
rpm -U <path to new package>
- On Ubuntu:
dpkg -i <path to new package>
- On RHEL / CentOS or
SLES:
- Run
configure.sh
to update the configuration for the new package:$ /opt/mapr/server/configure.sh -R --noRecalcMem
- On all nodes where the service is installed, start the
service:
maprcli node services -name livy -action start -nodes <ip_address>