[jboss-jira] [JBoss JIRA] Commented: (JGRP-911) STREAMING_STATE_TRANSFER: investigate use of UDP datagrams instead of TCP socket

Wed Apr 1 10:17:22 EDT 2009

    [ https://jira.jboss.org/jira/browse/JGRP-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460011#action_12460011 ] 

Vladimir Blagojevic commented on JGRP-911:
------------------------------------------

If use_default_transport property of pbcast.STREAMING_STATE_TRANSFER is set to true streaming state transfer will use normal messages to transfer state. This approach besides being completely transparent to application is also firewall friendly. However, as expected, tcp sockets have better performance. 

If default transport is used users can set another property - buffer_queue_size. This is the total state buffer size state producer is allowed to fill before being blocked until state receiver can process messages. The default value is 81920 bytes. 

> STREAMING_STATE_TRANSFER: investigate use of UDP datagrams instead of TCP socket
> --------------------------------------------------------------------------------
>
>                 Key: JGRP-911
>                 URL: https://jira.jboss.org/jira/browse/JGRP-911
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Vladimir Blagojevic
>             Fix For: 2.6.9, 2.8
>
>
> We currently use TCP server and client sockets to transfer state with STREAMING_STATE_TRANSFER. Add an option to use the default transport (could be TCP, could be UDP).
> State provider:
> - Write state into an output stream
> - The output stream generates unicast messages of a fixed size and sends them to the state receiver 
> State receiver:
> - Provides an input stream
> - The app reads data off of that stream
> - The received message chunks are placed into the input stream
> Might be more firewall friendly and causes less config overhead (e.g. punching of holes for the TCP conn in the FW).

-- 
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