wade

MapR Patch Release - June 2016

Blog Post created by wade on Jun 30, 2016

Get Notified of New Release & Patch Announcements

 

MapR Patch Release - June 2016

The following list of patches are interim patches released between maintenance release cycles. Each patch released (mid month) is cumulative in nature and includes prior patches released for the branch used.

 

 

 

 

5.1.0

 

Patch ID: mapr-patch-5.1.0.37549.GA-38657.x86_64

 

 

Bug 23106

 

Details

On an un-secure cluster, C client applications were able to impersonate even when the:

* MAPR_IMPERSONATION_ENABLED environment variable was not set to true

* Impersonating user did not have a file under /opt/mapr/conf/proxy

 

Resolution

With this fix, to enable impersonation on an unsecure cluster for C client applications, the MAPR_IMPERSONATION_ENABLED environment variable must be set to true and the impersonating user must have a file under /opt/mapr/conf/proxy​.

 

 

Bug 23382

 

Details

CLDB failed over with an exception when a node with stale containers was removed.

 

Resolution

With this fix, a node with stale containers can be removed successfully from the cluster and CLDB exceptions are not thrown.

 

 

Bug 23473

 

Details

In the following type of situation in MapR-DB, the first of a series of puts for a row would succeed, while the remaining puts in the series would fail without errors:

1. A tablet T is split into T1 and T. The dbclient still has tablet T cached with the original key range.

2. The dbclient issues a series of puts against a rowkey that used to be in T, but which is now in T1.

3. The server returns an ERANGE error for the first put, but not for the remaining puts in the series.

4. The dbclient retries the first put and succeeds, but does not retry the remaining puts because the dbclient never received the ERANGE error for those puts.

This problem could occur for different types of errors that applied to all of the puts issued together for a single row.

 

Resolution

With this fix, the server returns the relevant error message for all of the puts in a series for a single row.

 

 

Bug 23541

 

Details

A ddlopen of libmapr_pam.so using immediate symbol resolution threw an undefined symbol error.

 

Resolution

An updated libmapr_pam.so has been provided that links to libpam.so.

 

 

 

 

5.0.0

 

Patch ID: mapr-patch-5.0.0.32987.GA-38652.x86_64

 

Bug 20186

 

Details

The MapR dbclient logged ESTALE (Stale file handle) errors for successful operations on binary tables when MapR-DB client applications followed these steps:

  1. User X initiated the truncation of a binary table.

  2. User X issued an operation (get/put/scan, etc) against the table while MapR-DB was in the process of deleting the table, recreating it, and then refreshing inode information.

 

The attempt to modify the table was unsuccessful and the dbclient logged an ESTALE error. However, the dbclient retried the operation after the truncation process was over and successfully modified the table.

 

Resolution

With this fix, the dbclient no longer logs the ESTALE error before retrying an action on a table after the truncation process is finished.

 

 

Bug 23382

 

Details

CLDB failed over with an exception when a node with stale containers was removed.

 

Resolution

With this fix, a node with stale containers can be removed successfully from the cluster and CLDB exceptions are not thrown.

 

 

Bug 23473

 

Details

In the following type of situation in MapR-DB, the first of a series of puts for a row would succeed, while the remaining puts in the series would fail without errors:

1. A tablet T is split into T1 and T. The dbclient still has tablet T cached with the original key range.

2. The dbclient issues a series of puts against a rowkey that used to be in T, but which is now in T1.

3. The server returns an ERANGE error for the first put, but not for the remaining puts in the series.

4. The dbclient retries the first put and succeeds, but does not retry the remaining puts because the dbclient never received the ERANGE error for those puts.

This problem could occur for different types of errors that applied to all of the puts issued together for a single row.

 

Resolution

With this fix, the server returns the relevant error message for all of the puts in a series for a single row.

 

 

Bug 23541

 

Details

A ddlopen of libmapr_pam.so using immediate symbol resolution threw an undefined symbol error.

 

Resolution

An updated libmapr_pam.so has been provided that links to libpam.so.

 

 

4.1.0

 

 

Bug 20186

 

Details

The MapR dbclient logged ESTALE (Stale file handle) errors for successful operations on binary tables when MapR-DB client applications followed these steps:

  1. User X initiated the truncation of a binary table.

  2. User X issued an operation (get/put/scan, etc) against the table while MapR-DB was in the process of deleting the table, recreating it, and then refreshing inode information.

 

The attempt to modify the table was unsuccessful and the dbclient logged an ESTALE error. However, the dbclient retried the operation after the truncation process was over and successfully modified the table.

 

Resolution

With this fix, the dbclient no longer logs the ESTALE error before retrying an action on a table after the truncation process is finished.

 

 

Bug 23228

 

Details

In Hadoop 2.5.1, a MRv2 job was not committed until all tasks were complete. Therefore, large MRv2 Mapreduce jobs could take long time to commit even when

the job itself completed after a much shorter amount of time.

 

Resolution

With this fix, MAPREDUCE-4815 is backported into Hadoop 2.5.1. This patch includes a new fileoutputcommitter algorithm that improves performance. To enable the new algorithm, set mapreduce.fileoutputcommitter.algorithm.version to 2 in the mapred-site.xml or during job submission.

 

 

Bug 23382

 

Details

CLDB failed over with an exception when a node with stale containers was removed.

 

Resolution

With this fix, a node with stale containers can be removed successfully from the cluster and CLDB exceptions are not thrown.

 

 

Bug 23473

 

Details

In the following type of situation in MapR-DB, the first of a series of puts for a row would succeed, while the remaining puts in the series would fail without errors:

1. A tablet T is split into T1 and T. The dbclient still has tablet T cached with the original key range.

2. The dbclient issues a series of puts against a rowkey that used to be in T, but which is now in T1.

3. The server returns an ERANGE error for the first put, but not for the remaining puts in the series.

4. The dbclient retries the first put and succeeds, but does not retry the remaining puts because the dbclient never received the ERANGE error for those puts.

This problem could occur for different types of errors that applied to all of the puts issued together for a single row.

 

Resolution

With this fix, the server returns the relevant error message for all of the puts in a series for a single row.

 

 

Bug 23541

 

Details

A ddlopen of libmapr_pam.so using immediate symbol resolution threw an undefined symbol error.

 

Resolution

An updated libmapr_pam.so has been provided that links to libpam.so.

 

 

Bug 23545

 

Details

MapReduce Application Master did not honor the binding port range specified through the yarn.app.mapreduce.am.job.client.port-range property.

 

Resolution

With the fix, MapReduce Application Master honors the binding port range specified by the yarn.app.mapreduce.am.job.client.port-range property.

 

 

 

4.0.2

 

 

Bug 23382

 

Details

CLDB failed over with an exception when a node with stale containers was removed.

 

Resolution

With this fix, a node with stale containers can be removed successfully from the cluster and CLDB exceptions are not thrown.

 

 

Bug 23541

 

Details

A ddlopen of libmapr_pam.so using immediate symbol resolution threw an undefined symbol error.

 

Resolution

An updated libmapr_pam.so has been provided that links to libpam.so.

 

 

Bug 23545

 

Details

MapReduce Application Master did not honor the binding port range specified through the yarn.app.mapreduce.am.job.client.port-range property.

 

Resolution

With the fix, MapReduce Application Master honors the binding port range specified by the yarn.app.mapreduce.am.job.client.port-range property.

Outcomes