On 9/20/18 5:40 AM, Tom Pantelis wrote:
On Thu, Sep 20, 2018 at 1:45 AM Jamo Luhrsen mailto:jluhr...@gmail.com>> wrote:
> No - not with the default INFO logging. In order to dig deeper we need
to enable targeted debug, in this
> case org.opendaylight.controller.cluster.datastore.
On Thu, Sep 20, 2018 at 3:38 AM Vratko Polák
wrote:
> > It really isn't necessary that the new owner stays the same
>
>
> For some applications it does not matter.
>
> For other applications (such as openflow)
>
> each owner change means the old owner has to disconnect
>
> from the device and the
> It really isn't necessary that the new owner stays the same
For some applications it does not matter.
For other applications (such as openflow)
each owner change means the old owner has to disconnect
from the device and the new owner has to connect.
That can be expensive, and in worst case
On 09/19/2018 02:36 PM, Tom Pantelis wrote:
On Wed, Sep 19, 2018 at 4:46 PM Jamo Luhrsen mailto:jluhr...@gmail.com>> wrote:
\
> Anyway we'll need to enable debug for
org.opendaylight.controller.cluster.datastore.entityownership. I would
suggest to
> pull out that test on
On Wed, Sep 19, 2018 at 4:46 PM Jamo Luhrsen wrote:
> \
> > Anyway we'll need to enable debug
> for org.opendaylight.controller.cluster.datastore.entityownership. I would
> suggest to
> > pull out that test on its own like you've done before (run it standalone
> in sandbox I guess). Also delete
On 09/19/2018 11:39 AM, Tom Pantelis wrote:
It really isn't necessary that the new owner stays the same - it's more of an efficiency - in the end, all that really
matters is that there is *an* owner when the smoke clears. I'm not sure if it's guaranteed the owner won't change after
re-join (I
Tom, et al
we finally have our controller clustering jobs split to ask
vs tell. I'm going to stay with the focus on oxygen for now.
this job has a single failure:
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/controller-csit-3node-clustering-ask-all-oxygen/1/robot-plugin/log.html.g
