Known Issues

5.2.2

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

MCS
MON-4833 You cannot modify the username and password values with blank values in the SMTP settings page using the MCS. If you modify the username and password values with blank values using the CLI, the MCS SMTP settings page will continue to show the old values.

5.2.1

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

Installation and Configuration Issues
16155 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: 
    /opt/mapr/conf/mapr-clusters.conf
  2. Run configure.sh.
16216 When you run configure.sh 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.
MapR Streams
22621 MapR Streams does not support Windows 32-bit client.

5.2.0

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

Installation and Configuration Issues
16155 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: 
    /opt/mapr/conf/mapr-clusters.conf
  2. Run configure.sh.
16216 When you run configure.sh 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.
MapR Client
23624 The same MapR client can access both secure and nonsecure clusters; however, a MapR client that is configured to access a secure cluster can access a nonsecure cluster only if these conditions are met:
  • The secure cluster must be listed first in mapr-clusters.conf.
  • A user must obtain a ticket for the secure cluster even if the user wants to access only the nonsecure cluster.
MapR Streams
22621 MapR Streams does not support Windows 32-bit client.
MapR File System
22905 The tailf command does not work. So, when reading a file that is growing, use tail -f instead of tailf.
MapR Monitoring
OTSDB-72 Issue: The memory allocated to OpenTSDB can be insufficient, resulting in empty graphs and out-of-memory or GC overhead limit exceeded errors.
Workaround: Increase the default memory for OpenTSDB by making the following changes on all OpenTSDB nodes:
  1. Edit the /opt/maprconf/conf.d/warden.opentsdb.conf file to change:
    service.heapsize.max=2000
service.heapsize.min=2000

    to

    service.heapsize.max=6000
service.heapsize.min=6000
  2. Edit the /opt/mapr/opentsdb/opentsdb-*/etc/init.d/opentsdb file to change:
    $
{JVMXMX:=-Xmx2000m -Xss1m -XX:MaxMetaspaceSize=128m}

    to

    $
{JVMXMX:=-Xmx6000m -Xss1m -XX:MaxMetaspaceSize=128m}
  3. Restart the OpenTSDB service:
    maprcli node services -name opentsdb -nodes <space-separated list of OpenTSDB nodes> -action restart
23685 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
14696/15100 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