Confd doesn't rollback if client drop connection during netconf operation

General
1

HI

It seems confd continues commiting those configuration change even client have got disconnected the tcp socket before getting response. I observed it for netconf to create config nodes.
Next time the client try to do same commit then got config already exists. So I would like to ask if there is any way to config the behavior so Confd will do the rollback in that case.

Thanks for the answer
Charlie

2

If the transaction went past the “point of no return” before the client connection was lost, the transaction was committed. Search for “point of no return” in this WP for details: Whitepaper – Managing Distributed Systems Using NETCONF and RESTCONF Transactions