Package org.jgroups.protocols
Class DAISYCHAIN
java.lang.Object
org.jgroups.stack.Protocol
org.jgroups.protocols.DAISYCHAIN
Implementation of daisy chaining. Multicast messages are sent to our neighbor, which sends them to its neighbor etc.
A TTL restricts the number of times a message is forwarded. The advantage of daisy chaining is that - for
point-to-point transports such as TCP - we can avoid the N-1 issue: when A sends a multicast message to 10
members, it needs to send it 9 times. With daisy chaining, it sends it 1 time, and in the next round, can already
send another message. This leads to much better throughput, see the ref in the JIRA.
Should be inserted just above MERGE2, in TCP based configurations.
JIRA: https://jira.jboss.org/browse/JGRP-1021
- Since:
- 2.11
- Author:
- Bela Ban
-
Nested Class Summary
Nested Classes -
Field Summary
FieldsModifier and TypeFieldDescriptionprotected Executorprotected booleanprotected BlockingQueue<Message> protected Addressintintprotected Addressprotected Executorprotected booleanprotected BlockingQueue<Message> protected int -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionAn event is to be sent down the stack.intintprotected voidhandleView(View view) voidinit()Called after instance has been created (null constructor) and before protocol is started.protected Objectvoidstart()This method is called on aChannel.connect(String).voidstop()This method is called on aChannel.disconnect().An event was received from the layer below.Methods inherited from class org.jgroups.stack.Protocol
destroy, downThreadEnabled, dumpStats, enableStats, getConfigurableObjects, getDownProtocol, getId, getLevel, getName, getProperties, getProtocolStack, getSocketFactory, getThreadFactory, getTransport, getUpProtocol, getValue, isErgonomics, printStats, providedDownServices, providedUpServices, requiredDownServices, requiredUpServices, resetStats, setDownProtocol, setErgonomics, setId, setLevel, setProperties, setPropertiesInternal, setProperty, setProtocolStack, setSocketFactory, setUpProtocol, setValue, setValues, statsEnabled, upThreadEnabled
-
Field Details
-
local_addr
-
next
-
view_size
protected int view_size -
default_pool
-
oob_pool
-
send_queue
-
forward_queue
-
forward
protected volatile boolean forward -
running
protected volatile boolean running -
msgs_forwarded
public int msgs_forwarded -
msgs_sent
public int msgs_sent
-
-
Constructor Details
-
DAISYCHAIN
public DAISYCHAIN()
-
-
Method Details
-
getElementsInForwardQueue
public int getElementsInForwardQueue() -
getElementsInSendQueue
public int getElementsInSendQueue() -
init
Description copied from class:ProtocolCalled after instance has been created (null constructor) and before protocol is started. Properties are already set. Other protocols are not yet connected and events cannot yet be sent. -
start
Description copied from class:ProtocolThis method is called on aChannel.connect(String). Starts work. Protocols are connected and queues are ready to receive events. Will be called from bottom to top. This call will replace the START and START_OK events.- Overrides:
startin classProtocol- Throws:
Exception- Thrown if protocol cannot be started successfully. This will cause the ProtocolStack to fail, soChannel.connect(String)will throw an exception
-
stop
public void stop()Description copied from class:ProtocolThis method is called on aChannel.disconnect(). Stops work (e.g. by closing multicast socket). Will be called from top to bottom. This means that at the time of the method invocation the neighbor protocol below is still working. This method will replace the STOP, STOP_OK, CLEANUP and CLEANUP_OK events. The ProtocolStack guarantees that when this method is called all messages in the down queue will have been flushed -
down
Description copied from class:ProtocolAn event is to be sent down the stack. The layer may want to examine its type and perform some action on it, depending on the event's type. If the event is a message MSG, then the layer may need to add a header to it (or do nothing at all) before sending it down the stack usingdown_prot.down(). In case of a GET_ADDRESS event (which tries to retrieve the stack's address from one of the bottom layers), the layer may need to send a new response event back up the stack usingup_prot.up(). -
up
Description copied from class:ProtocolAn event was received from the layer below. Usually the current layer will want to examine the event type and - depending on its type - perform some computation (e.g. removing headers from a MSG event type, or updating the internal membership list when receiving a VIEW_CHANGE event). Finally the event is either a) discarded, or b) an event is sent down the stack usingdown_prot.down()or c) the event (or another event) is sent up the stack usingup_prot.up(). -
processQueues
-
handleView
-