Applying a Patch Manually

HPE Ezmeral Data Fabric patches are version-specific and cumulative. Each patch contains the code fixes that were included in the previous patch for that release version.

ATTENTION
Note the following before you proceed:
  • A fabric installed by using the legacy installer must be upgraded by using the legacy installer only. The legacy installer does not install the Keycloak service. You must use your organization's Keycloak service for production environments. Similarly, the life cycle of a fabric installed by using the Data Fabric UI should be solely managed by using the Data Fabric UI. If you still go ahead and add patch by using the legacy installer (the installer is installed on all the nodes of the fabric), future updates/upgrades to the fabric will remove the patch as the Data Fabric UI does not know the patch was installed.
  • The mapr-keycloak package available with HPE Ezmeral Data Fabric is only a placeholder service in the Data Fabric UI, and is not recommended for a production environment. You must use your organization's Keycloak service in a production environment. The legacy installer does not install the Keycloak service.
Before applying a patch, note these considerations:
  • For patch-download information, see Applying a Patch.
  • The steps for patching the Control System are different from the steps for patching core. See Special Considerations for Control System Patches.
  • You can also apply a patch using the Installer. See Applying a Patch Using the Installer.
  • A patch for a given software version can be removed, and an older patch for the same software version can be installed. However, rolling back a cluster from a newer release version to an older version is not supported.
  • Different types of patches are available, and some patches can only be installed on specific nodes:
    Patch Type Install on These Nodes
    mapr-patch All control and data nodes
    mapr-patch-client HPE Ezmeral Data Fabric client nodes only
    mapr-patch-loopbacknfs Any node where POSIX is supported
    mapr-patch-nfs4server Any node where NFSv4 is supported
    mapr-patch-posix-client-basic Any node where FUSE POSIX is supported
    mapr-patch-posix-client-platinum Any node where FUSE POSIX is supported

Applying a patch is a three-step process:

Step 1: Verify Cluster Readiness for a PatchStep 2: Apply the Patch to Data NodesStep 3: Apply the Patch to CLDB Nodes

When you apply a patch to the cluster, the patched files along with original files (non-patched) are copied to the /opt/mapr/.patch folder. In the /opt/mapr/.patch folder, the file ending with .O is the original file (non-patched) and the file ending with .<patch_number> is the patched version. Therefore, if there is a file under /opt/mapr/.patch/lib/, you can compare that with the corresponding file under /opt/mapr/lib/ by using the md5sum command to verify that the patch was successfully deployed.

If you need more information or if you encounter any problems with patch installation, contact HPE Support.