[jboss-jira] [JBoss JIRA] (JGRP-1868) Size of XMIT_REQ is not limited
Bela Ban (JIRA)
issues at jboss.org
Wed Aug 6 05:20:30 EDT 2014
[ https://issues.jboss.org/browse/JGRP-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990645#comment-12990645 ]
Bela Ban edited comment on JGRP-1868 at 8/6/14 5:18 AM:
--------------------------------------------------------
To prevent having to use a seond {{FRAG}}, we could
* Send multiple XMIT-REQs, whose SeqnoList arg is size-limited to 60K (if transport == UDP). {{SeqnoList.size()}} computes the exact size.
* Send am XMIT-REQ only for the oldest N seqnos (as mentioned by Radim)
* (Re-)implement retransmission backoffs to reduce xmit traffic. However, this requires additional state in the xmit tables
* Compress SeqnoList to use less space, e.g. by using bitmaps/sets
was (Author: belaban):
To prevent having to use a seond {{FRAG}}, we could
* Send multiple XMIT-REQs, whose SeqnoList arg is size-limited to 60K (if transport == UDP). {{SeqnoList.size()}} computes the exact size.
* Send am XMIT-REQ only for the oldest N seqnos (as mentioned by Radim)
* (Re-)implement retransmission backoffs to reduce xmit traffic. However, this requires additional state in the xmit tables.
> Size of XMIT_REQ is not limited
> -------------------------------
>
> Key: JGRP-1868
> URL: https://issues.jboss.org/browse/JGRP-1868
> Project: JGroups
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Radim Vansa
> Assignee: Bela Ban
> Fix For: 3.6
>
>
> When UNICAST3 sends XMIT_REQ, it serializes SeqnoList as payload without any limits upon its size. If there are too many missing messages, the XMIT_REQ grows over TP.max_bundle_size and cannot be sent at all.
> {code}
> JGRP000029: edg-perf03-10774: failed sending message to edg-perf01-63702 (64072 bytes): java.lang.Exception: message size (64072) is greater than max bundling size (64000). Set the fragmentation/bundle size in FRAG and TP correctly, headers: UNICAST3: XMIT_REQ, seqno=0, UDP: [channel_name=default]
> {code}
> It's also undesirable to resend thousands of messages, as the receiver likely cannot process them all at once and only few of them will be actually processed. Therefore only X oldest ones (in order to cleanup the tables) should be resent.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the jboss-jira
mailing list