Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1300621 - Duplicate key with auto increment
Duplicate key with auto increment
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mariadb (Show other bugs)
7.4
All Linux
urgent Severity urgent
: rc
: ---
Assigned To: Jakub Dorňák
qe-baseos-daemons
: Patch, ZStream
Depends On:
Blocks: 1303946
  Show dependency treegraph
 
Reported: 2016-01-21 05:00 EST by Rupesh Patel
Modified: 2016-11-03 16:46 EDT (History)
11 users (show)

See Also:
Fixed In Version: mariadb-5.5.44-3.el7
Doc Type: Bug Fix
Doc Text:
When more than one INSERT operation was executed concurrently on a non-empty InnoDB table with an AUTO_INCREMENT column defined as a primary key immediately after starting MariaDB, a race condition could occur. As a consequence, one of the concurrent INSERT operations failed with a "Duplicate key" error message. A patch has been applied to prevent the race condition. Now, each row inserted as a result of the concurrent INSERT operations receives a unique primary key, and the operations no longer fail in this scenario.
Story Points: ---
Clone Of:
: 1303946 (view as bug list)
Environment:
Last Closed: 2016-11-03 16:46:29 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2595 normal SHIPPED_LIVE Important: mariadb security and bug fix update 2016-11-03 08:11:21 EDT

  None (edit)
Description Rupesh Patel 2016-01-21 05:00:18 EST
Upstream found critical bug in recent releases and they have fixed it here.
https://mariadb.atlassian.net/browse/MDEV-8827

Upstream has fixed it in 5.5.47.
Comment 16 errata-xmlrpc 2016-11-03 16:46:29 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2595.html

Note You need to log in before you can comment on or make changes to this bug.