2018-08-09T06:17:47,637 | INFO |
opendaylight-cluster-data-shard-dispatcher-45 | Shard
| 214 - org.opendaylight.controller.sal-clustering-commons -
1.7.3.SNAPSHOT | member-1-shard-default-config (Candidate): Starting new
election term 14
All shards are in Candidate and thus haven't converged. This blocks other
bundles from starting. I assume you're testing the issue where a node
doesn't rejoin on restart - looks like you've hit it.
On Mon, Aug 13, 2018 at 7:49 PM, Jamo Luhrsen <jluhr...@gmail.com> wrote:
> Hi team,
>
> Does anyone know what happened here?
>
> https://paste.fedoraproject.org/paste/ynvKX0LCsFIPMf13AagrQg
>
> I have a local script where I'm killing and restarting an ODL instance
> (just loading some controller level features) and polling for 2m to make
> sure it's up and repeating. It's in a 3 node cluster.
>
> making sure it's up means a 200 response and cluster SyncStatus == true.
>
> It's not the bug I'm looking to catch, but I wanted to ask about it
> just in case it's new and/or know.
>
> Seems that some bundles are not coming up.
>
> Thanks,
> JamO
> _______________________________________________
> 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
