It means preCommit/commit occurred out-of-order, eg

preCommit txn 1
preCommit txn 2
commit txn 2
commit txn 1

It's an internal problem in the CDS. We put a hack in Be to workaround it.
This patch in master https://git.opendaylight.org/gerrit/#/c/42728/
explains the scenario and implements a proper solution.

Muthu - feel free to review as I can't add you :)


On Thu, Aug 4, 2016 at 12:29 PM, Muthukumaran K <muthukumara...@ericsson.com
> wrote:

> Hi,
>
>
>
> I want to understand under which condition, this exception seen in
> InMemoryDataTree.java#commit is thrown ?
>
>
>
> Does this exception mean that a child is being added by one Txn for a
> parent which could have been deleted another Txn ?
>
>
>
> I checked related bug in OVSDB – https://bugs.opendaylight.org/
> show_bug.cgi?id=5062 which shows similar stack trace but could not
> conclude the condition of this exception
>
>
>
> Regards
>
> Muthu
>
>
>
> _______________________________________________
> controller-dev mailing list
> controller-dev@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/controller-dev
>
>
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Reply via email to