Missing functions in upstream bug #1118 Percona 5.6

Bug #1396336 reported by Chris Calender on 2014-11-25
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Server
Status tracked in 5.7
5.1
Undecided
Unassigned
5.5
Undecided
Unassigned
5.6
Wishlist
Unassigned
5.7
Undecided
Unassigned

Bug Description

Bug #1118 was included in 5.6.19-67.0 which caused our implementation of GET_LOCK break. We have long running connections that will get and release locks. The new functionality looks like it will increment a lock acquisition each time a GET_LOCK is called rather than just releasing the previous named lock and acquiring it again.

We have processes that can run for days over billions of records. Now the get/release lock count gets out of sync sometimes and causes the server to hang up. The data we are working on is the core IP for the company and it is very important that these types of problems do not occur.

I examined the 5.7 release functions which has as RELEASE_ALL_LOCKS()function that would make sure this doesn't happen. But this was not included in the upstream implementation of the feature in 5.6. Since the upgrade is really mandatory because of the security fixes included in 5.6.21, we would like to have this function added to support the #1118 inclusion.

You'll see mention of bug #1118 here:

http://www.percona.com/doc/percona-server/5.6/upstream-bug-fixes.html

Right, we have changed the function semantics in the middle of release series, I agree that it's a reasonable request.

tags: added: i48942
tags: added: get-lock
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers