Data Fabric FUSE-Based POSIX Client

Provides a brief description of the FUSE-based POSIX client.

The data-fabric FUSE-based POSIX client (either mapr-posix-client-basic or mapr-posix-client-platinum) allows app servers, web servers, and other client nodes and apps to read and write data directly and securely to a data-fabric cluster like a Linux filesystem.

The same data-fabric client can access both secure and nonsecure clusters; however, a data-fabric client that is configured to access a secure cluster can access a nonsecure cluster only if these conditions are met:

  1. The secure cluster must be listed in the mapr-clusters.conf file.

  2. A user must obtain a ticket for the secure cluster even if the user wants to access only the nonsecure cluster.

The FUSE-based data-fabric POSIX client runs as a userspace process to connect to one or more data-fabric clusters. The necessary FUSE (Filesystem in Userspace) library (libfuse) is bundled with the POSIX client package. With the installation of the POSIX client package, the data-fabric POSIX client performs operations such as read and write on the filesystem exposed by FUSE. The following diagram illustrates how the data-fabric FUSE-based POSIX client works.

The table below summarizes the differences between the POSIX loopback NFS client and the FUSE-based POSIX Basic and Platinum clients:

Data Fabric POSIX Loopback NFS Client Data Fabric FUSE-based POSIX Basic/Platinum Client
Throughput
  • 500MB/s for remote read/write
  • 1G/s for local read/write
Greater than 2G/s for remote and local read/write
Client OS Supported Linux and Ubuntu distributions only.
Installs On Node Type
  • Client node
  • Cluster node
Access to Cluster Must have direct network access to all data-fabric cluster nodes. Must have direct network access to all data-fabric cluster nodes. However, each client only supports up to 16 clusters.
Connection to File System
  • Proxied on host to regular data-fabric client traffic
  • Direct, no NFS for the HPE Ezmeral Data Fabric gateway
  • No single point of failure
Security Fully secured.
Caching Buffered writes are cached in the kernel. Buffered writes are cached (only in kernel >= 3.15) if writeback option is enabled.