Re: [tipc-discussion] TIPC_WITHDRAW event comes late

[Hung Ta <hu...@op...>]

Hi Ying,

On Mon, May 11, 2020 at 8:52 PM Ying Xue <yin...@wi...> wrote:

> Please validate whether it appears with the latest kernel.
>
> If you cannot, please provide more detailed info:
>
> 1. Capture TIPC packets with tcpdump tool;
>
 Attached


> 2. Provide dmesg log, but be sure each line of demeg logs should be

prefixed by timestamps.
>
 Attached


> 3. Print timestamp as well when you receive TIPC_WITHDRAW on user land.
>
 Test scenario:
1. Setting up 2 nodes for the cluster, and getting them up
2. Reboot node 1 at 11:12:20. At node 2: until 11:12:30 (after 10s) the
WITHDRAW (death) event came:
Wed May 13 11:12:30.339 2020 [clTipcNotification.c:395] (scI1.1040 :
AMF.TIPC.NOTIF.01502 :   INFO) Got node [death] notification (2) for node
[1]

I'm testing on the latest Ubuntu release (20.04 64 bits ,
kernel 5.4.0-29-generic)

Thanks.


>
> On 5/8/20 11:01 AM, Hung Ta wrote:
> > Hi TIPC experts,
> >
> > I'm using the TIPC library in my project which needs to be aware of a
> node
> > leaves the cluster.
> >
> > So, I use socket type AF_TIPC and SOCK_SEQPACKET and connect it
> > to TIPC_TOP_SRV.
> >
> > I tried to get several nodes up and then make one of them leave and then
> I
> > can see the event TIPC_WITHDRAW seen, but the issue is it comes very
> late,
> > in particular,  it comes about 10 seconds late after a node left the
> > cluster.
> > I'm using Ubuntu 16.04, kernel 4.4.0-87-generic.
> > The same issue also occurs in Ubuntu 14.04.
> >
> > Why is it too late?
> > Appreciate your help.
> >
> > Thanks and regards,
> > Hung
> >
> > _______________________________________________
> > tipc-discussion mailing list
> > tip...@li...
> > https://lists.sourceforge.net/lists/listinfo/tipc-discussion
> >
>