[jboss-jira] [JBoss JIRA] Commented: (JGRP-528) NAKACK: spurious retransmission requests
[
https://jira.jboss.org/jira/browse/JGRP-528?page=com.atlassian.jira.plugi...
]
Sien Kian Quah commented on JGRP-528:
-------------------------------------
Just a couple of questions on this issue, and hope someone could advice. (I'm sorry,
if this is not the correct place to ask questions - I'm new to using this website
account)
Basically my software is currently using version 2.4.1 SP1.
1) Using version 2.4.1 SP1, I've encountered this issue ( spurious retransmission
requests ) as well. Is this normal?
2) When this issue happened, the CPU shoot up to 100%. Will this issue ( spurious
retransmission requests ) caused CPU to shoot up to 100% ?
3) Is this issue solved in version 2.6.0?
4) If I upgrade to 2.4.1 SP4, will this issue happen, and caused CPU to shoot up to 100%
as well?
Thanks in advance.
NAKACK: spurious retransmission requests
-----------------------------------------
Key: JGRP-528
URL: https://jira.jboss.org/jira/browse/JGRP-528
Project: JGroups
Issue Type: Task
Affects Versions: 2.5
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 2.6
Every now and then, spurious retransmission requests are received:
NAKACK.handleXmitReq(): (requester=192.168.5.2:4397, local_addr=192.168.5.2:4393) message
192.168.5.2:4393::600 not found in retransmission table of 192.168.5.2:4393: [650 : 1050
(1100) (size=x, missing=0, highest stability=650)]
It turns out that message #600 *was* actually retransmitted correctly, but the
retransmission timer was cancelled too late, so that we got 1 or 2 spurious retransmit
requests for the same message.
This doesn't happen very frequently, and only under heavy load (e.g. 8 nodes, every
node sends 5M 5K messages with 500 threads).
Note that this issue DOES NOT LEAD TO INCORRECT BEHAVIOR !
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira