summaryrefslogtreecommitdiffstats
path: root/openstack/common/plugin/callbackplugin.py
diff options
context:
space:
mode:
authorMark McLoughlin <markmc@redhat.com>2013-02-20 23:08:50 +0000
committerMark McLoughlin <markmc@redhat.com>2013-02-20 23:16:22 +0000
commit6f9cef85353155538fe14e5025e2d0bab5cc63e4 (patch)
tree23598db753266a1a4f167c725d267a5d8b74ae59 /openstack/common/plugin/callbackplugin.py
parent7e6513dedc58577c187d69d576659bc7f2ed7a87 (diff)
downloadoslo-6f9cef85353155538fe14e5025e2d0bab5cc63e4.tar.gz
oslo-6f9cef85353155538fe14e5025e2d0bab5cc63e4.tar.xz
oslo-6f9cef85353155538fe14e5025e2d0bab5cc63e4.zip
Revert "Implement replay detection."
This reverts Ib0260a0c62e3d312d2e3448a125bed64d861319e (commit a603678) The issue we're trying to fix here is bug #1107064 - when using mirrored queues with AMQP, acks can be lost while a master is failing over to a slace causing the new slave to re-send messages which had previously been acked. The "replay detection" code applies to more than just amqp and also has the appearance of a security measure (e.g. the use of the term 'nonce') when clearly it serves no security purpose until we actually have message signing. Revert the "replay detection" approach in favour of the more targetted amqp bugfix. Change-Id: I8b8d15835c8b4c85cd388f5df08b60ff4c74e38d
Diffstat (limited to 'openstack/common/plugin/callbackplugin.py')
0 files changed, 0 insertions, 0 deletions