Ignore old messages sent to conductor

Registered by Ed Cranford on 2014-02-04

Conductor can at present receive updates via heartbeat and update_backup that could potentially arrive out of order, which means an instance's status or that of its backups could be corrupted should a message in the queue fall out of order, especially in the case when a user is employing multiple conductor workers. One proposal to avert this behavior is to attach a "sent" field to each message sent, and discard the ones that arrive to conductor after more recently-sent messages.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
Ed Cranford
Direction:
Needs approval
Assignee:
Ed Cranford
Definition:
New
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 2014.1
Started by
Nikhil Manchanda on 2014-02-05
Completed by
Michael Basnight on 2014-02-10

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/conductor-ignore-old-messages,n,z

Addressed by: https://review.openstack.org/67611
    Ignore outdated messages sent to conductor

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.