BUG-8620: handle direct commit and disconnect correctly 30/58430/3
authorRobert Varga <robert.varga@pantheon.tech>
Wed, 7 Jun 2017 16:08:28 +0000 (18:08 +0200)
committerTom Pantelis <tompantelis@gmail.com>
Wed, 7 Jun 2017 20:29:44 +0000 (20:29 +0000)
commitda42d2ffc8904b8dd24596cf6d918a0d30c8c521
tree093d850b04b18fc6f140ccbfc0e61543e77197ec
parent09630b9ae171a976301a795e745044ae58812df7
BUG-8620: handle direct commit and disconnect correctly

Transactions committed directly can complete in a disconnected
fashion as we are skipping the back-and-forth communication of the
three-phase commit. This period may involve shard leadership changes
and so we may end up in a situation where we are replaying a direct
commit request to a transaction which already completed -- which
raises a RequestFailure to make sure we do not do anything untoward.

In the specific case of direct commit, though, this is perfectly fine
and so update the callback to account for this case happening.

Change-Id: Ic60e69f0f58cc7c5a3ac869386dc12f856aa1f74
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/databroker/actors/dds/AbstractProxyTransaction.java

©2013 OpenDaylight, A Linux Foundation Collaborative Project. All Rights Reserved.
OpenDaylight is a registered trademark of The OpenDaylight Project, Inc.
Linux Foundation and OpenDaylight are registered trademarks of the Linux Foundation.
Linux is a registered trademark of Linus Torvalds.