X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=blobdiff_plain;ds=sidebyside;f=opendaylight%2Fmd-sal%2Fsal-distributed-datastore%2Fsrc%2Fmain%2Fjava%2Forg%2Fopendaylight%2Fcontroller%2Fcluster%2Fdatabroker%2Factors%2Fdds%2FClientTransaction.java;h=0a1c8be2471102db655b80359f63ebb5faa2cfd2;hb=refs%2Fchanges%2F99%2F47499%2F3;hp=f5f545a48e85af1c6faa255ee031b08934d1dcdc;hpb=98d1c5606bad9633ce5549bcd691a98c75abdf6a;p=controller.git diff --git a/opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/databroker/actors/dds/ClientTransaction.java b/opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/databroker/actors/dds/ClientTransaction.java index f5f545a48e..0a1c8be247 100644 --- a/opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/databroker/actors/dds/ClientTransaction.java +++ b/opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/databroker/actors/dds/ClientTransaction.java @@ -27,22 +27,28 @@ import org.slf4j.LoggerFactory; /** * Client-side view of a free-standing transaction. * + *

* This interface is used by the world outside of the actor system and in the actor system it is manifested via * its client actor. That requires some state transfer with {@link DistributedDataStoreClientBehavior}. In order to * reduce request latency, all messages are carbon-copied (and enqueued first) to the client actor. * + *

* It is internally composed of multiple {@link RemoteProxyTransaction}s, each responsible for a component shard. * + *

* Implementation is quite a bit complex, and involves cooperation with {@link AbstractClientHistory} for tracking * gaps in transaction identifiers seen by backends. * + *

* These gaps need to be accounted for in the transaction setup message sent to a particular backend, so it can verify * that the requested transaction is in-sequence. This is critical in ensuring that transactions (which are independent * entities from message queueing perspective) do not get reodered -- thus allowing multiple in-flight transactions. * + *

* Alternative would be to force visibility by sending an abort request to all potential backends, but that would mean * that even empty transactions increase load on all shards -- which would be a scalability issue. * + *

* Yet another alternative would be to introduce inter-transaction dependencies to the queueing layer in client actor, * but that would require additional indirection and complexity. * @@ -62,8 +68,7 @@ public final class ClientTransaction extends LocalAbortable implements Identifia private volatile int state = OPEN_STATE; - ClientTransaction(final DistributedDataStoreClientBehavior client, final AbstractClientHistory parent, - final TransactionIdentifier transactionId) { + ClientTransaction(final AbstractClientHistory parent, final TransactionIdentifier transactionId) { this.transactionId = Preconditions.checkNotNull(transactionId); this.parent = Preconditions.checkNotNull(parent); } @@ -72,18 +77,16 @@ public final class ClientTransaction extends LocalAbortable implements Identifia Preconditions.checkState(state == OPEN_STATE, "Transaction %s is closed", transactionId); } + private AbstractProxyTransaction createProxy(final Long shard) { + return parent.createTransactionProxy(transactionId, shard); + } + private AbstractProxyTransaction ensureProxy(final YangInstanceIdentifier path) { checkNotClosed(); final ModuleShardBackendResolver resolver = parent.getClient().resolver(); final Long shard = resolver.resolveShardForPath(path); - AbstractProxyTransaction ret = proxies.get(shard); - if (ret == null) { - ret = AbstractProxyTransaction.create(parent.getClient(), parent.getHistoryForCookie(shard), - transactionId.getTransactionId(), resolver.getFutureBackendInfo(shard)); - proxies.put(shard, ret); - } - return ret; + return proxies.computeIfAbsent(shard, this::createProxy); } @Override