Bug 1303946
Summary: | Duplicate key with auto increment | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
Component: | mariadb | Assignee: | Jakub Dorňák <jdornak> |
Status: | CLOSED ERRATA | QA Contact: | Branislav Blaškovič <bblaskov> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 7.4 | CC: | baptiste.agasse, bblaskov, databases-maint, fkrska, hhorak, jdornak, jprokes, lkuprova, mkolaja, rupatel, thoger, troels |
Target Milestone: | rc | Keywords: | Patch, ZStream |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | mariadb-5.5.47-1.el7_2 | 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: | 1300621 | Environment: | |
Last Closed: | 2016-03-31 22:00:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1300621 | ||
Bug Blocks: |
Description
Marcel Kolaja
2016-02-02 13:35:18 UTC
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-0534.html |