[EnMasse] Disconnect from time to time

[Ulf Lilleengen]

On Wed, Mar 27, 2019 at 10:57 AM Gordon Sim <gsim at redhat.com> wrote:

> On 27/03/2019 9:44 am, Bob Claerhout wrote:
> > Hi Ulf,
> >
> > Thanks for the fast responses. I'm not experiencing this on a regular
> basis.
> > However, an error happened again this morning. Hereby the logging:
> >
> >     The Qdrouter logging: https://pastebin.com/QB1xbLdn
>
> There are two router pods, right? Could you paste the logs from the
> other router as well?
>
>
According to the admin pod logs it looks like there seems to be only 1.
Also this is a sharded topic broker from looking at the broker logs.

Ignoring all the tracing stuff, i can't find any notion of disconnection
happening from the router side in the logs. From the broker log:

2019-03-27T03:40:41.970Z INFO  [ProtonClientConnectionManager] Connection
messaging-aloxy/172.30.9.50:56671 destroyed

Whereas the 2 entries in the router in the same time is:

2019-03-27 03:40:37.417193 +0000 SERVER (info) [94473]: Accepted connection
to 0.0.0.0:55671 from 10.128.0.67:36180
2019-03-27 03:40:45.478579 +0000 SERVER (info) [94474]: Accepted connection
to 0.0.0.0:56711 from 10.128.0.1:36070

There are these messages from the lost link I guess:

[0x7f7af4085850]:1 <- @detach(22) [handle=8, closed=true, error=@error(29)
[condition=:"qd:routed-link-lost", description="Connectivity to the peer
container was lost"]]
[0x7f7ae8190e20]:0 -> @detach(22) [handle=0, closed=true, error=@error(29)
[condition=:"qd:routed-link-lost", description="Connectivity to the peer
container was lost"]]

I wonder if the improved logging in router 1.6.0 (in the upcoming 0.27.0
release) could shed some more light on this.

Best regards,

Ulf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/enmasse/attachments/20190327/0d7455df/attachment.htm>