Redis driver claims failing in smoke test

Bug #1367033 reported by Kurt Griffiths
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zaqar
Fix Released
Critical
Kurt Griffiths

Bug Description

When smoke-testing the redis driver via zaqar-bench, I noted this output which does not appear when running the same test against the mongo driver:

Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: A claim was specified, but the message is not currently claimed.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
Could not delete messages: This message is claimed; it cannot be deleted without a valid claim ID.
C

Kurt Griffiths (kgriffs)
Changed in zaqar:
milestone: none → juno-rc1
assignee: nobody → Kurt Griffiths (kgriffs)
importance: Undecided → Critical
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to zaqar (master)

Fix proposed to branch: master
Review: https://review.openstack.org/119978

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to zaqar (master)

Reviewed: https://review.openstack.org/119978
Committed: https://git.openstack.org/cgit/openstack/zaqar/commit/?id=22ea4d0a33db9ea068e16cef67936f96b5f5cce5
Submitter: Jenkins
Branch: master

commit 22ea4d0a33db9ea068e16cef67936f96b5f5cce5
Author: kgriffs <email address hidden>
Date: Mon Sep 8 22:00:46 2014 -0500

    Fix messages getting reclaimed in the Redis driver

    A race condition was discovered during smoke testing of the Redis
    driver that can cause messages to be reclaimed. The problem was that
    between getting a list of "active" messages, and setting watch on
    them, they could be claimed by another process without the first
    process being notified.

    This patch gaurds against the race condition by moving the query for
    active messages to execute after the watch has been set. In this way,
    if another process commits a claim in the meantime, the first process
    will be notified so that it can try again with a new batch of active
    messages.

    Change-Id: I27a7e88ef0c3f9f8b1c5e653caec0fc503905e13
    Closes-Bug: #1367033

Changed in zaqar:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in zaqar:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
no longer affects: zaqar/juno
Changed in zaqar:
milestone: juno-rc1 → 2014.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.