HPE Ezmeral Data Fabric 6.2 is In Maintenance and transitions to "End of Maintenance" in June 2024. Please see the latest documentation.

About Release 6.2
This site contains documentation for HPE Ezmeral Data Fabric release 6.2 including installation, configuration, administration, and reference content, as well as content for the associated bundled ecosystem components and drivers.
6.2 Installation
This section contains information about installing and upgrading HPE Ezmeral Data Fabric software. It also contains information about how to migrate data and applications from an Apache Hadoop cluster to a HPE Ezmeral Data Fabric cluster.
- Planning the Cluster
  Describes information and factors used in planning your cluster.
- Installing Core and Ecosystem Components
  Describes how to install HPE Ezmeral Data Fabric software and ecosystem components with or without the Installer.
- Installing the File Migration Service on the Edge Cluster
  Describes how to install the File Migration service on CentOS nodes.
- Installing the HPE Ezmeral Data Fabric File Store
  Describes how to install File Store software with or without the Installer.
- Installing Kubernetes Interfaces for Data Fabric
  This section describes how to plan for and install the Container Storage Interface (CSI) Storage Plugin and the Kubernetes Interfaces for Data Fabric FlexVolume Driver.
- Upgrading Core or EEP Components
  Depending on your current configuration, you may choose to upgrade the release version (core), ecosystem components, clients, or monitoring components.
  - Upgrade Workflows (Release 6.1.x to 6.2)
    This section describes three common methods for upgrading from one core release to another. The workflows in this section introduce you to the high-level steps for each method and provide links to pages showing more detail.
  - Upgrading Core
    Describes the process of upgrading core.
    - Upgrading and Your License
      You do not need a new license to upgrade an HPE Ezmeral Data Fabric cluster. However, it's a good idea to check your cluster license periodically and renew the license before it expires.
    - Core Upgrade Process
      When you upgrade core, you will also upgrade a number of cluster components.
    - Planning Your Core Upgrade
      Describes how to develop a successful plan for your upgrade process.
    - When Upgrading Core with the Installer Requires an OS Upgrade
      Helps you decide if an OS upgrade is needed when you are using the Installer to upgrade to core 6.2.0 or later.
    - Upgrading Your Linux Operating System
      Upgrading to a new release of the HPE Ezmeral Data Fabric sometimes requires you to upgrade your Linux operating system. This page has pointers to more information about OS upgrades.
    - Preparing to Upgrade Core
      Complete these pre-upgrade steps for core.
    - Upgrading Core With the Installer
      If the cluster that you want to upgrade was installed using the Installer, use the Installer to upgrade core.
    - Upgrading Core Without the Installer
      You can upgrade core without using the Installer.
    - Finishing the Core Upgrade
      This section provides post-upgrade steps for core.
      - Post-Upgrade Steps for Core
        After upgrading core, several manual steps are required.
        Considerations for Upgrades Using the Installer
        If you use the Installer to upgrade the cluster, some post-upgrade steps for core do not need to be performed. This page describes the post-upgrade steps that are performed by the Installer and the steps that you must perform manually.
        Step 1: Restart and Check Cluster Services
        After upgrading core using either a manual offline or rolling upgrade method (not upgrading with the Installer) and upgrading your ecosystem components, configure and restart the cluster and services.
        Step 2: Manually Update Configuration Files
        After upgrading core using a manual offline or rolling upgrade method, update your configuration files.
        Step 3: Upgrade Clients
        After you upgrade your cluster, you may also need to upgrade your data-fabric client or POSIX client.
        Upgrading the Data Fabric Client
        Depending on which data-fabric client you want to update, you will either need to install and reconfigure or perform a package upgrade.
        Upgrading the Data Fabric POSIX loopbacknfs Client
        Perform a package upgrade to get a newer version of the data-fabric POSIX loopbacknfs Client.
        Upgrading the loopbacknfs POSIX Client on a Linux Server
        This section describes how to upgrade the loopbacknfs POSIX Client on a Linux server.
        Troubleshooting loopbacknfs POSIX Client Upgrades
        If you are having difficulty upgrading the POSIX client, it might be due to a shared-memory-segment lock.
        Migrating to FUSE-Based POSIX Clients
        This section describes how to migrate from the loopbacknfs POSIX client to the FUSE-based POSIX basic client.
        Upgrading the FUSE POSIX Client on a Linux Server
        This section describes how to upgrade the FUSE POSIX client on a Linux server.
        Step 4: Enable New Features
        Describes the new features to enable after upgrading core without the Installer using a manual offline or rolling upgrade method.
        Step 5: Update Hadoop Configuration File
        When manually upgrading (manual offline and manual rolling upgrade) from version 4.x to version 6.x and switching from classic mode to YARN mode, you must manually update the Hadoop configuration file.
      - Installing Additional Core Features
        Some features can require additional configuration or the installation of additional packages after an upgrade to a new release.
      - Securing the Upgraded Cluster
        Nonsecure clusters can be secured after the upgrade process.
  - Upgrading Ezmeral Ecosystem Packs
    Describes how to upgrade Ezmeral Ecosystem Packs (EEPs), either as part of a core upgrade or to take advantage of a new EEP for the current version of core.
  - Preparing the Cluster for a Maintenance Update
    This section identifies how to prepare for applying either a minor update or a patch.
  - Performing a Maintenance Update
    Perform a maintenance update when you want to upgrade to a new patch version of core or apply a patch.
- Setting Up Clients and Services
  Describes how to set up and use interfaces to an HPE Ezmeral Data Fabric cluster from a client computer.
- Setting Up the Control System
  Describes how to configure and access the Control System.
- Migrating to the HPE Ezmeral Data Fabric
  Provides instructions for migrating business-critical data and applications from an Apache Hadoop cluster to an HPE Ezmeral Data Fabric cluster.
- Applying a Patch
  You can apply a patch by using the Installer, by using the command line (a manual process), or by using an Installer Stanza.
6.2 Data Fabric
HPE Ezmeral Data Fabric is the industry-leading data platform for AI and analytics that solves enterprise business needs.
6.2 Administration
This section describes how to manage the nodes and services that make up a cluster.
6.2 Development
This section contains information related to application development for Ezmeral ecosystem components and HPE Ezmeral Data Fabric products, including the file system, Database (Key-Value and JSON), and Event Streams.
Other Docs
This section contains release-independent information, including: Installer documentation, Ecosystem release notes, interoperability matrices, security vulnerabilities, and links to other data-fabric version documentation.
Glossary
Definitions for commonly used terms in MapR Converged Data Platform environments.

Upgrading the loopbacknfs POSIX Client on a Linux Server

This section describes how to upgrade the loopbacknfs POSIX Client on a Linux server.

About this task

To upgrade the loopbacknfs POSIX client on a RHEL, SLES, or Ubuntu server, you must upgrade the mapr-loopbacknfs package.

NOTE To migrate the POSIX Client to a FUSE-based POSIX client, see Migrating to FUSE-based POSIX Clients.

Procedure

Stop the mapr-loopbacknfs service.
```
service mapr-loopbacknfs stop
```
Remove any currently installed client patches. For example:
- On RedHat / CentOS: yum remove mapr-patch-loopbacknfs
- On SLES: zypper remove mapr-patch-loopbacknfs
- On Ubuntu: apt-get remove mapr-patch-loopbacknfs
Upgrade the mapr-loopbacknfs package.
- On RedHat / CentOS: yum update mapr-loopbacknfs
- On SLES: zypper update mapr-loopbacknfs
- On Ubuntu: apt-get install mapr-loopbacknfs
Update the cluster configuration information in the mapr-loopbacknfs.new file.
```
vi /usr/local/mapr-loopbacknfs/initscripts/mapr-loopbacknfs.new
```

Copy mapr-loopbacknfs.new to the mapr-loopbacknfs script

cp
/usr/local/mapr-loopbacknfs/initscripts/mapr-loopbacknfs.new
/usr/local/mapr-loopbacknfs/initscripts/mapr-loopbacknfs

Start the loopbacknfs service.
```
service mapr-loopbacknfs start
```
Check the status of the loopbacknfs service.
```
service mapr-loopbacknfs status
```