HAHT - Missed action mitigation during DSD failover

Bug #1600013 reported by Eric K
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
congress
Fix Released
Low
Eric K

Bug Description

Implement changes to mitigate missed actions during DSD failover.

Please see spec and blueprint for more information.
https://github.com/openstack/congress-specs/blob/master/specs/newton/high-availability-design.rst
https://blueprints.launchpad.net/congress/+spec/high-availability-design

Tags: haht
Eric K (ekcs)
Changed in congress:
assignee: nobody → Eric K (ekcs)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to congress (master)

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

Changed in congress:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to congress (master)

Reviewed: https://review.openstack.org/352670
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=8b299e410a7082f46b2ba41561ddc8000e86ff36
Submitter: Jenkins
Branch: master

commit 8b299e410a7082f46b2ba41561ddc8000e86ff36
Author: Eric K <email address hidden>
Date: Thu Aug 11 00:43:24 2016 -0700

    HAHT - Mitigate missed action during DSD failover

    Added option to retry execute action to mitigate missed actions in
    case of DSD failover or transport failures.

    Also changed action execution to be asynchronous so that PE can
    continue to operate while waiting for action execution to finish
    This seems to be a good idea even without retry because depending
    on the action, execution could take minutes, preventing the PE from
    responding to new data/requests if done synchronously. Some tempest
    tests may need updating for change to asynchronous.

    New config options:
    - execute_action_retry to enable retry
    - execute_action_retry_timeout to set timeout until giving up

    Closes-Bug: 1600013
    Partially implements blueprint: high-availability-design

    Change-Id: I782118d2d3b683ae979b8748935a1bd8b7bc99dd

Changed in congress:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/congress 4.0.0.0b3

This issue was fixed in the openstack/congress 4.0.0.0b3 development milestone.

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.