Known Issues

You may encounter the following known issues after upgrading to Version 5.2.0.

Installation and Configuration Issues

When you run with the -HS option on client nodes, the mapred-site.xml is re-generated and does not retain existing user settings. To work around this problem, use the -R option in the command.
In order to reconfigure a Mac client from secure mode to non-secure mode (or vice versa), you must follow these steps:
  1. Manually remove the entry for the current cluster from:
  2. Run

If you enable centralized logging on a cluster that was using YARN log aggregation in Version 4.0.1 prior to upgrading to version 4.1.0, you can no longer access previously aggregated MapReduce logs from the HistoryServer UI.

Workaround: Perform the following steps to view previously aggregated MapReduce logs from the History Server UI:

  1. Use the yarn logs command to retrieve the logs for each MapReduce application. The output of this command contains stdout, stderr, syslog with specific delimiters.
  2. Parse the output of yarn logs command to create syslog, stdout, stderr files using UNIX tools such as sed or awk.
  3. Add the syslog, stdout, stderr files to the centralized logging directory with the following directory hierarchy:
    /var/mapr/local/<NodeManager node>/logs/yarn/userlogs/application_<applicationID>/container_<containerID>/

You will need to create the application and container directories and provide the user that submitted the application the proper permissions on the files and directories.

For example, if usera submitted the application, usera should have the following permissions on the directories and log files:
  • Application directories:
    drwxr-s--- 5 usera mapr 4096 2015-01-07 11:32 /var/mapr/local/<id>
  • Container directories:
    drwxr-s--- - usera mapr 3 2015-01-07 11:32 /var/mapr/local/<id>/container_<id>
  • Log files:
    -rw-r----- 2 usera mapr 290 2015-01-07 11:32 /var/mapr/local/<id>/container_<id>/stderr
Note: After you complete the workaround, you will also be able to run maprcli job linklogs on these logs.

MapR Streams

MapR Streams does not support Windows 32-bit client.

MapR File System

The tailf command does not work. So, when reading a file that is growing, use tail -f instead of tailf.

MapR Monitoring

The mapr.cldb.storage_pools_offline metric only includes storage pools that have been offline for more than one hour.

Metrics Database Issues

Note the following limitations with job metrics:
  • You cannot use the Metrics Database to record activity for applications that run in YARN (MRv2). The database only supports MRv1 jobs.
  • MRv1 metrics are not supported on any RedHat 7.x system.

Resource Manager Issues

When automatic or manual ResourceManager failover is enabled and a job is submitted with impersonation turned ON by a user without impersonation privileges, the job submission eventually times out instead of returning an appropriate error. This behavior does not affect standard ecosystem services such as HiveServer because they are configured to run as the mapr user (with impersonation allowed). However, this problem does affect non-ecosystem applications or services that attempt to submit jobs with impersonation turned ON. MapR recommends that customers add the user in question to the impersonation list so that the job can proceed.
When several jobs are submitted and the ResourceManager is using the ZKRMStateStore for failover, the cluster may experience ZooKeeper timeouts and instability. MapR recommends that customers always use the FileSystemRMStateStore to support ResourceManager HA. See Recovery for the ResourceManager.