- **Milestone**: 5.22.01 --> future
---
** [tickets:#3280] dtm: loss of TCP connection requires node reboot**
**Status:** unassigned
**Milestone:** future
**Created:** Fri Aug 27, 2021 11:33 AM UTC by Mohan Kanakam
**Last Updated:** Sun Jan 23, 2022 09:58 PM UTC
**Owner:** Mohan Kanakam
Some time we see loss of TCP connection among payloads or among controller and
payloads in the cluster.
Example: If we have 2 controllers and 10 payloads(starting from PL-3 to PL-10),
we see TCP connection loss at PL-4 among PL-5. The connection of PL-4 with
other payloads remains established.
We also see connection loss at PL-7 with SC-2, the connection of PL-7 with
other nodes remains established. This result in PL-7 reboot when controller
failover happens i.e. SC-1 fails and SC-2 takes Act role. PL-7 thinks that
there was a single controller in the cluster and it reboots.
This could be reproduced by adding iptables rule to drop the packets.
So, the expected behavior is dtmd on PL-4/PL-5 can retry the connection for few
times before declaring the node is down.
The only drawback with this approach is that it will delay the application
failover time or even controller failover time.
Any suggestion on it ??
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
