wade

MapR Patch Release - May 2016

Blog Post created by wade on May 26, 2016

Get Notified of New Release & Patch Announcements

 

MapR Patch Release - May 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.

 

 

Patch Installer - End of Support - May 20, 2016 (learn how to manually install patches)

 

 

5.1.0

 

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

 

Bug 22491

 

Details

A typographical error in log messages prevented MapR support from accurately confirming that container resync errors were causing mirroring failures.

 

Resolution

With this fix, the typographical errors are corrected.

 

Bug 22829

 

Details

On installations with two MFS instances per node on (SSD-based) clusters, instead of assigning one license per node, MFS was using one license per instance. For example, a 10 node cluster with SSDs required 20 licenses instead of 10 licenses.

 

Resolution

With this fix, MFS will no longer assign multiple licenses to a node if more than one MFS instance is running on that node.

 

Bug 22873

 

Details

Occasionally, writes to MapR-FS by C client applications were not visible immediately after a flush. Therefore, these writes appeared to be missing.

 

Resolution

With this fix, the data inconsistency issue is resolved.

 

Bug 22949

 

Details

Occasionally, C client applications connected to MapR-FS experienced short reads during concurrent reads or concurrent reads and writes.

 

Resolution

With this fix, the short read issue is resolved.

 

Bug 22978

 

Details

If posix-client packages (mapr-posix-client-basic/platinum) were installed on both a MapR core cluster and a client node, the mapr-patch-posix-client patch did not work as expected.

 

Resolution

With this fix, the posix client patch can be applied to both the MapR cluster and the client node.

 

Bug 23178

 

Details

Consumer applications reading messages from topics in MapR Streams generate globally unique identifiers (GUIDs) that the server can use to identify individual consumers. Consumers running on OS X could occasionally generate GUIDs in formats that the server would not recognize.

 

Resolution

With this fix, consumers running on OS X always generate GUIDs in the correct format.

 

Bug 23186

 

Details

When a MapR-FS client application written in C called hdfsDisconnect(), the corresponding file system handle was not deleted, resulting in memory leaks.

 

Resolution

With this fix, file handles are now deleted when hdfsDisconnect() is called.

 

Bug 23192

 

Description

User credentials were not set explicitly whenever a client application accessed a MapR-DB table, which caused an EACCES error in the following type of situation:

 

For connecting to a single MapR cluster, a client application written in C creates two connection objects (connA and connB), using separate user credentials (for userA and userB) for each connection object.

 

A single application thread is used for table operations with both connA and connB. This thread performs these operations:

 

1. As userA, the thread creates table X via connA. The MapR dbclient, which mediates connections between client applications and MapR clusters running MapR-DB, caches the credentials for userA in thread local storage.

 

2. As userB, the thread deletes table Y via connB. The dbclient overwrites userA's credentials in thread local storage with the credentials for userB.

 

3. As userA, the thread attempts a put operation on table X. Before attempting to access the table with userA's credentials, the dbclient does not first overwrite the credentials in thread local storage. Because the stored credentials are for userB, the attempt to access the table fails.

 

Resolution

With this fix, the dbclient overwrites the credentials in thread local storage with the current user's credentials before attempting to access tables.

 

Bug 23215

 

Description

When a client application written in C successfully deleted a table in MapR-DB, error messages such as the following would be logged:

  2016-04-27 14:30:58,0688 ERROR Client fs/client/fileclient/cc/client.cc:2372

  Thread: 1120 Unlink failed for file /user/temp/test.table, error Invalid

  argument(22)

  2016-04-27 14:30:58,0688 ERROR Inode fs/client/fileclient/cc/inode.cc:485

  Thread: 1120 Unlink failed on file /user/temp/test.table with error 22

 

Resolution

With this fix, such error messages are no longer logged.

 

Bug 23303

 

Details

In C client applications for MapR-FS, calling hdfsConnectAsUserNewInstance() with an invalid user and then calling the same function call with a valid user caused mfs to core.

 

Resolution

With this fix, when all further calls with a valid user is made, the memory corruption (because of failed user resolution during the first call) will not result in core dump.

 

Bug 23304

 

Details

Running the ls command from a valid (working) cluster returned the following error when the clusters.conf file included an invalid (non-working) cluster entry:

ls: cannot open directory .: No such file or directory

 

Resolution

With this fix, the ls command no longer returns the aforementioned error if the clusters.conf file includes an invalid (non-working) cluster entry.

 

Bug 23311

 

Details

If a table was a source in table replication, an incremental bulk load of one or more non-replicated column families would cause the mfs service to core.

 

For example, suppose a source table contained the column families cf1, cf2, and cf3. Only cf3 was being replicated. If an incremental bulk load was started for cf1 and cf2, the mfs service cored.

 

Resolution

With this fix, the mfs service no longer cores in this type of situation.

 

Bug 23312

 

Details

The duration specified while generating cross-cluster tickets was not being set and the default duration of 14 days was being applied instead.

 

Resolution

With this fix, for:

* Admin generated cross-cluster and service tickets:

  * The duration specified while generating a ticket will now be honored.

  * The default duration is now LIFETIME.

Note: Service and cross-cluster tickets are now not bounded by the CLDB duration properties.

* Password authenticated tickets, if duration is:

  * Specified, the specified duration will be honored.

  * Not specified, the default duration configured as CLDB properties will be used.

The maprlogin print command will now print ticket of any type.

 

Bug 23315

 

Details

Many GetXAttr (get extended attribute) calls (for file ACEs) were made on the NFS mount irrespective of the file type. This resulted in a lot of GetXAttr calls on the NFS mount for normal file operations.

 

Resolution

With this fix, GetXAttr calls will only be made for a special file (.dfs_attributes).

 

 

 

5.0.0

 

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

 

Bug 21613

 

Details

Resynchronization hung after an RPC failure because replicas did not handle the RPC failure scenario.

 

Resolution

After the fix, resynchronization fails gracefully after an RPC failure.

 

 

Bug 22491

 

Details

A typographical error in log messages prevented MapR support from accurately confirming that container resync errors were causing mirroring failures.

 

Resolution

With this fix, the typographical errors are corrected.

 

 

Bug 23311

 

Details

If a table was a source in table replication, an incremental bulk load of one or more non-replicated column families would cause the mfs service to core.

 

For example, suppose a source table contained the column families cf1, cf2, and cf3. Only cf3 was being replicated. If an incremental bulk load was started for cf1 and cf2, the mfs service cored.

 

Resolution

With this fix, the mfs service no longer cores in this type of situation.

 

 

4.1.0

Prepare for MapR 4.x End of Maintenance by January 2017

 

Patch ID: mapr-patch-4.1.0.31175.GA-38213.x86_64.rpm

                mapr-patch-4.1.0.31175.GA-38212.x86_64.deb

 

Bug 21975

 

Details

Mirroring failed during source volume snapshot creation and returned a -1 error when a cross-cluster security ticket was used for mirroring.

 

Resolution

With this fix, mirroring no longer fails during source volume snapshot creation when a cross-cluster security ticket is used for mirroring.

 

Bug 22024

 

Details

Secure cross-cluster mirroring failed to complete because a container resynchronization procedure was rejected by the MapR-FS.

 

Resolution

With this fix, the MapR-FS allows all the resynchronization procedures that are required when cross-cluster mirroring occurs on secure clusters.

Outcomes