Fix free-standing transaction lookup with module-based shards 92/80392/3
authorRobert Varga <robert.varga@pantheon.tech>
Tue, 19 Feb 2019 12:50:04 +0000 (13:50 +0100)
committerTom Pantelis <tompantelis@gmail.com>
Tue, 19 Feb 2019 17:20:54 +0000 (17:20 +0000)
commit8528c8bea98570731e9b4e508507c59cbe93d1c0
tree1c120b486a77307902eacb3f5656458ba28acf56
parentff73c17be7840781085c48efb28612f045fe1d9f
Fix free-standing transaction lookup with module-based shards

When we have a combination of tell-based protocol with module-based
shards, the frontend will use the cookie within LocalHistoryIdentifier,
making it potentially non-zero.

The backend tracks free-standing transactions under a local history,
which has cookie set to zero, hence it will not match when we attempt
to look it up for the purposes commit/abort/purge -- leading to
mismatched leader state for these transactions.

Change-Id: Ic4a493d0728b8de288a779d8c97a157584dc76bb
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/datastore/FrontendClientMetadataBuilder.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.