-
1. Re: Flooding "not found in retransmission table" in server log too much in cluster and making application slow.
pferraro Feb 8, 2020 8:54 AM (in response to dheeraj.mishra)You probably need to disable use_mcast_xmit (which was inadvertently enabled in some older WF versions).
e.g.
<stack name="...">
<transport type="UDP" ... />
<!-- ... -->
<protocol type="pbcast.NAKACK2">
<property name="use_mcast_xmit_req">false</property>
</protocol>
<!-- ... -->
</stack>
-
2. Re: Flooding "not found in retransmission table" in server log too much in cluster and making application slow.
dheeraj.mishra Feb 7, 2020 11:39 AM (in response to pferraro)Thanks Paul!
I tried this option but no luck!
I changed all standalone.xml file with below parameter and tried. still i see the error and slowness. one thing which I observed that still i see use_mcast_xmit value true in Jconsole JMX.
<protocol type="pbcast.NAKACK2">
<property name="use_mcast_xmit">false</property>
</protocol>
-
3. Re: Flooding "not found in retransmission table" in server log too much in cluster and making application slow.
pferraro Feb 8, 2020 8:53 AM (in response to dheeraj.mishra)My apologies, the property to disable should be "use_mcast_xmit_req".
-
4. Re: Flooding "not found in retransmission table" in server log too much in cluster and making application slow.
dheeraj.mishra Feb 8, 2020 11:11 AM (in response to pferraro)Thanks Paul for your response!
i tried to configure parameters like below but still I see value is true in Jconsole. did i miss anything?
<stacks>
<stack name="udp">
<transport type="UDP" socket-binding="jgroups-udp"/>
<protocol type="PING"/>
<protocol type="MERGE3"/>
<protocol type="FD_SOCK"/>
<protocol type="FD_ALL"/>
<protocol type="VERIFY_SUSPECT"/>
<protocol type="pbcast.NAKACK2">
<property name="use_mcast_xmit">false</property>
<property name="use_mcast_xmit_req">false</property>
</protocol>
<protocol type="UNICAST3"/>
<protocol type="pbcast.STABLE"/>
<protocol type="pbcast.GMS"/>
<protocol type="UFC"/>
<protocol type="MFC"/>
<protocol type="FRAG2"/>
</stack>
</stacks>
-
5. Re: Flooding "not found in retransmission table" in server log too much in cluster and making application slow.
pferraro Feb 10, 2020 6:38 AM (in response to dheeraj.mishra)I fear the only workaround options are:
- Use the legacy protocol configuration for NAKACK2, i.e. <protocol type="org.jgroups.protocols.pbcast.NAKACK2"/>
- Cherry pick this fix and rebuild: WFLY-9473 Custom NAKACK2 automatically enables use_mcast_xmit/use_mca… · wildfly/wildfly@106ed30 · GitHub
- Disable multicast for UDP (i.e. use a socket binding that does not supply a multicast address).
- Upgrade to a more recent version of WildFly.
-
6. Re: Flooding "not found in retransmission table" in server log too much in cluster and making application slow.
dheeraj.mishra Feb 12, 2020 1:34 AM (in response to pferraro)Thanks much Paul! it is working now with option 1 change. now we dont see any re-transmission related WARN/ERROR in log.
thanks again.