When there is a large burst of write transactions executed on a transaction chain, the last couple of transactions do not seem to be properly handled:

a) after existing from the burst loop, the last 1-2 transactions do not get propagated into the data store, and the app callbacks (from transaction Futures) are not called.

b) after closing the transaction chain, data from the last 1-2 transaction appears in the data store, but the app callbacks are still not called.

The code to reproduce this behavior is in https://git.opendaylight.org/gerrit/#/c/14872/.

After building the dsbenchmark application according to Gerrit #14872, the behavior can be triggered by a REST POST call to: http://localhost:8181/restconf/operations/dsbenchmark:start-test,

with payload:

{
"input":

}