[infinispan-dev] MFC/UFC credits in default config

Radim Vansa rvansa at redhat.com
Thu Jan 3 10:55:56 EST 2013


| | 
| | This sounds good, using JGroups cachewrapper I could just do GET on
| | one slave in a loop, right? The only modification required is that
| | the JGroupsWrapper.get should do dispatcher.callRemoteMethods(...)
| | with all members instead of just single invocation. And maybe the
| | I think I could grab some time for this next week.
| | 
| | 
| | I think to make it really like state transfer you'd have to keep
| | one
| | GET target, but make all nodes pick the same target (e.g. the first
| | node) and make the key really big. Making all nodes targets would
| | work as well, but you'd have to do that on only one node to mimic a
| | single joiner asking for state.
| | 
| 
| Single joiner flooded by data was the problem, wasn't it? We could
| test both, of course, single joiner to big cluster and
| superelasticity where many nodes try to request data from single
| node. Still, the second one is not problematic for flow control,
| because the source will supply the data as fast as it can but all
| nodes can handle the fraction of data.
| 
| 
| 1-to-n GET requests with huge values or n-to-1 GET requests with huge
| keys should be roughly equivalent, as they'd both test many nodes
| sending messages to a single node (i.e. the joiner). I don't think
| it's worth testing the many joiners case either.
| 

Right, I have overlooked the "key" and assumed the value.

Radim


More information about the infinispan-dev mailing list