[jboss-jira] [JBoss JIRA] Resolved: (JGRP-289) Optimize stacks.xml
Bela Ban (JIRA)
jira-events at jboss.com
Fri Sep 1 10:53:43 EDT 2006
[ http://jira.jboss.com/jira/browse/JGRP-289?page=all ]
Bela Ban resolved JGRP-289.
---------------------------
Resolution: Done
> Optimize stacks.xml
> -------------------
>
> Key: JGRP-289
> URL: http://jira.jboss.com/jira/browse/JGRP-289
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 2.3 SP1
> Reporter: Bela Ban
> Assigned To: Bela Ban
> Fix For: 2.4
>
>
> We decided we want 4 configurations in stacks.xml:
> 1. fc-fast-minimalthreads
> 2. tcp (copy of the above, with TCP/TCPPING as transport)
> 3. fc-fast-minimalthreads-sync: alternative to #1, without FC and with message bundling disabled
> 4. tcp-sync: copy of #2, without FC and with message bundling disabled
> * The default stacks (fc-fast and tcp) have FC and message bundling is enabled
> * All stacks have FLUSH: because we use the Multiplexer, state transfer requires FLUSH
> * VIEW_SYNC will be removed (because we use FLUSH, this is redundant)
> * STREAMING_STATE_TRANSFER will be the default state transfer protocol
> o STATE_TRANSFER is there, but commented
> o According to Vladimir, these 2 protocols can be used interchangeably, the correct setState() and getState() methods will always be called
> * For the TCP-based stack
> o we use TCP_NIO as transport
> o Discovery is TCPPING: we pass the list of hosts as a system property, default is localhost
> * Vladimir and I will look at the resulting stacks.xml, and once it is correct, pass it on to Brian and Manik, so it can be tested with clustering and JBossCache
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list