The MapR Container for Developers is a Docker container that enables you to create a single-node MapR cluster. The container is lightweight and designed to run on your laptop. It requires no additional configuration for you to connect your clients, also running on your laptop, to the cluster.

The MapR Sandbox for Hadoop is a fully-functional single-node cluster that gently introduces business analysts, current and aspiring Hadoop developers, and administrators (database, system, and Hadoop) to the big data capabilities of Hadoop and its ecosystem.

Immediately after a master CLDB failover, users were able to remove a node
which had not yet registered with the new master CLDB.

With this fix, node cannot be removed for up to 15 minutes after a master
CLDB failover.

CLDB

29588

CLDB deleted wrong CID 1 causing CLDB volume to be wiped out

FileClient

22571

To use the MapR Client on Windows, it was necessary to set up the spoof user
username, uid, and gid in the core-site.xml file because these
properties were needed for translating cluster uid back to username (for job
submission).

With this fix, you need not set up the spoof user username, uid, and gid in the
core-site.xml file as username is available via the
ticket.

FileClient

23880

When multiple applications attempt to load the same MapR
native library using the root class loader, an exception was returned
because MapR native library can be loaded only once and an application
had already successfully loaded the MapR native library.

With this fix, an exception is not returned when applications
try to load an already loaded MapR native library.

FileClient

24140

On Windows, MapRClient generates core for Python APIs

FileClient

24247

FSDataInputStream the number of bytes read, possibly zero, or -1 if reach
end-of-stream not met

The MapR FUSE-based POSIX client required user/group to exist before allowing
creation of files in MapR-FS with those UIDs/GIDs.

With this fix, the MapR FUSE-based POSIX allows file creation in MapR-FS with
UIDs/GIDs that may not exist on the cluster or the client host.

FUSE-based POSIX Client

28910

When enabling the setgid bit on a file, if the the primary group set in the
executing process did not match the actual group of the file, then POSIX-compliant
file systems proceeded without throwing an error.

With this fix, the file system now gives EPERM error when setting the setgid
bit on file, if the primary group of the executing process does not match the actual
group of the file.

FUSE-based POSIX Client

28914

Unlink operation sometimes left the file in inconsistent state when accessed
using the FUSE-based POSIX client.

With this fix, the unlink operation will succeed and the file cannot be accessed.

FS:Hardlinks

24238

Multi-mfs crashes at mapr::fs::Container::IAllocFromAg

FS:Mirror2RW

20644

Mirror schedule stop with inuse flag 0

FS:Mirror2RW

25308

mfs asserts in GetChildAttrInodeGotten()

FS:Replication

25147

Mfs detected deadlock condition during container replication and result to
server restart