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.
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.
- Administering Users and Clusters
  Lists topics that help manage a data-fabric cluster.
- Administering Nodes
  Provides a synopsis of managing nodes in a cluster.
- Administering Volumes
  This section provide information about how to organize and manage data using volumes, a unique feature of HPE Ezmeral Data Fabric clusters.
- Administering Files and Directories
- Administering Tables
  Administration of the HPE Ezmeral Data Fabric Database is done primarily via the command line (maprcli) or with the Managed Control System (MCS). Regardless of whether the HPE Ezmeral Data Fabric Database table is used for binary files or JSON documents, the same types of commands are used with slightly different parameter options. HPE Ezmeral Data Fabric Database administration is associated with tables, columns and column families, and table regions.
- Administering Streams
- Administering Data Fabric Gateways
  A HPE Ezmeral Data Fabric gateway mediates one-way communication between a source HPE Ezmeral Data Fabric cluster and a destination cluster. You can replicate HPE Ezmeral Data Fabric Database tables (binary and JSON) and HPE Ezmeral Data Fabric Streams streams. HPE Ezmeral Data Fabric gateways also apply updates from JSON tables to their secondary indexes and propagate Change Data Capture (CDC) logs.
- Administering Services
- Monitoring the Cluster
  This section describes how to monitor the health and performance of a MapR cluster.
- Configuring Security
  Describes how to configure security and manage secure clusters.
- Managing Secure Clusters
  Provides procedures that will enable you to use MapR clusters securely.
- Administering the Data Access Gateway
  The HPE Ezmeral Data Fabric Data Access Gateway is a service that acts as a proxy and gateway for translating requests between lightweight client applications and the HPE Ezmeral Data Fabric cluster. This section describes considerations when upgrading the service, how to modify configuration settings, and how to administer and manage the service.
- Planning for High Availability
- Administrator's Reference
  This section contains in-depth reference information for the administrator.
  - maprcli and REST API Syntax
    This section provides information about the HPE Ezmeral Data Fabric command API. Most commands can be run on the command-line interface (CLI), or by making REST requests programmatically or in a browser.
  - Utilities
    Contains information about various scripts and utilities, that help setup, maintain, and monitor clusters.
  - Configuration Files
    This section contains reference information about various configuration files.
  - Alarms Reference
    The pages in this section provide details about all of the types of alarms.
  - HPE Ezmeral Data Fabric Environment
    This section provides information associated with the Data Fabric environment.
    - HPE Ezmeral Data Fabric Parameters
      Describes Data Fabric parameters and their default values.
    - Default HPE Ezmeral Data Fabric Configurations
      Lists sources from which default Data Fabric configuration parameters are derived.
    - Environment Variables
      Describes the environment variables specific to the HPE Ezmeral Data Fabric.
    - Ports Used by HPE Ezmeral Data Fabric Software
      Lists the ports used by Data Fabric services.
    - Log Files
      Lists the log files for each HPE Ezmeral Data Fabric component.
      - Increasing Log Retention
      - Setting the Tracing Level
      - Configuring Profiling for Operations
      - Archiving CLDB Logs
      - Enabling Runtime Logging
      - Viewing Audit Logs
      - Viewing Application Logs
      - Viewing the Service Log
        Esplains how to view service logs using Kibana.
    - Cluster Maintenance Schedule
      Lists a sample maintenance schedule for the cluster.
    - Language Support for HPE Ezmeral Data Fabric Database Tables
      This section lists the human languages that HPE Ezmeral Data Fabric tables can store, retrieve, and process.
- Troubleshooting Cluster Administration
  Lists the common errors and their solutions.
- Best Practices for Backing Up HPE Ezmeral Data Fabric Information
  Lists the best practices and performance considerations to follow when backing up HPE Ezmeral Data Fabric information.
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.

Configuring Profiling for Operations

To check the amount of time it took to complete each operation (from the time of submission), enable profiling for client RPC and file system operations. To enable profiling for:

Client RPC, run the following command:
```
fcdebug -s <shmid> -m ClntProfileRpc -1 DEBUG
```
TIP For more information, see fcdebug.
Enabling profiling for the client RPC will allow you to determine, for each RPC, the amount of time it took to receive a response after submitting the request.
file system operations, run the following command:
```
maprcli trace setlevel -module FSProfile -level debug
```
TIP For more information, see maprcli.
Enabling profiling for file system operations will allow you to determine the amount of time it took file system to process each operation.

By default, profiling is disabled for both client RPC and file system operations. Once enabled, the log for:

Client RPC should look similar to the following:

2016-06-16 10:58:04,6404 DEBUG ClntProfileRpc
fs/client/fileclient/cc/client.cc:3483 Thread: 32188 Profile: CltRpcDone:
server 10.10.100.196:5692 took 1 msec error 0 FID 2125.34.262486  Getattr
          
2016-06-16 11:13:55,7480 DEBUG ClntProfileRpc
fs/client/fileclient/cc/client.cc:3202 Thread: 32161 Profile: CltRpcDone:
server 10.10.100.196:5692 took 1 msec error 0 FID 2125.16.2  PathWalkPlus path
abc

file system should look similar to the following:

2016-06-19 15:51:05,0231 DEBUG FSProfile unlink.cc:2456 OP unlink: localTm 34
elapsedTm 34 client 10.10.100.196 err 0 PFID: 1.32.131398 name
unreachableFSIdTable itype Regular
          
2016-06-19 15:51:11,0249 DEBUG FSProfile writev3.cc:1296 OP Write: localTm 13
elapsedTm 13 client 10.10.100.196 err 0 FID: 2121.532.2364014 off 29234 count
1424
          
2016-06-19 15:51:08,1184 DEBUG FSProfile readdir.cc:505 OP ReadDir: elapsedTm
28 client 10.10.100.196 err 0 FID: 2121.16.2 Isplus true

For example, to check the time it took for a read RPC, run the following command:

# cat /opt/mapr/logs/ffs.log* | grep -nrui "CltRpcDone" | grep -nrui "read" | less
1009:1014:2016-06-16 11:21:51,8203 DEBUG ClntProfileRpc
fs/client/fileclient/cc/client.cc:4900 Thread: 32151 Profile: CltRpcDone:
server10.10.100.196:5660 took 0 msec for Proc Read error 0 FID 2182.32.131232
off 7143424 len 131072 name 2125.34.262486