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.
  - Container Storage Interface (CSI) Storage Plugin
    This section describes how to plan for, install, and upgrade the Container Storage Interface (CSI) Storage Plugin.
  - MapR Data Fabric for Kubernetes FlexVolume Driver
    Serves as a pointer on how to plan for, install, and upgrade data-fabric for Kubernetes.
    - Planning
      Points to information you should review before installing or using the data-fabric for Kubernetes FlexVolume driver.
    - Installing
      This section describes the steps you must take to prepare for installation and install the configuration files for the HPE Ezmeral Data Fabric for Kubernetes FlexVolume driver.
    - Upgrading
      This section describes how to upgrade the plug-in and dynamic provisioner, or upgrade Pods with attached volumes.
- 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.
- 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 MapR Data Fabric for Kubernetes

This section describes how to upgrade the plug-in and dynamic provisioner, or upgrade Pods with attached volumes.

Upgrading the Plug-in and Provisioner

Before upgrading the plug-in, stop any Pods using the plug-in. You may want to quiesce any traffic hitting the Pod before shutdown. Failure to shut down the Pods before replacing the plug-in can lead to the Pod not being able to access its data until it is restarted.

Removing the plug-in does not kill existing Pods. The Pods should only lose their mounted storage when a new version of the plug-in is installed and the libraries used to communicate with MapR software are deleted.

Upgrading the provisioner does not require stopping Pods, but dynamic provisioning (creating MapR volumes for new PersistentVolumeClaims) will be unavailable during the provisioner upgrade.

Use these steps to upgrade the plug-in:

Stop any Pods using the the plug-in to be upgraded. Before shutting down the Pod, you might want to quiesce any traffic hitting the Pod.
NOTE If any Pods that use the MapR Data Fabric for Kubernetes are not shut down during the plug-in upgrade, those Pods will have mount access removed and will need to be deleted and re-created as new Pods. If existing Pods need to be removed or are stuck in the Terminating state, you can delete them forcefully by using the kubectl delete pod command:
```
kubectl delete pod <pod-name> -n <pod-namespace> --force --grace-period=0
```
Download the new plug-in. See Downloads (FlexVolume).
Delete the old plug-in:
```
kubectl delete -f kdf-<old_plugin>.yaml
```
Deploy the new plugin:
```
kubectl create -f kdf-<new_plugin>.yaml
```

Upgrading Pods with Attached Volumes

Pods with mounted volumes can be patched in place. See Update API Objects in Place Using kubectl patch. Volumes will disappear only when the Pod is deleted. Patching a Pod does not affect the mount. When a Pod is deleted, a volume disappears. However, if you delete a Pod using a PersistentVolume and you leave the PVC alive, you can remount the PersistentVolumeClaim and its PersistentVolume with a new Pod. In this scenario, there is no disruption or need to recreate the PersistentVolume.