Package org.jgroups.protocols
Class BATCH
java.lang.Object
org.jgroups.stack.Protocol
org.jgroups.protocols.BATCH
- All Implemented Interfaces:
Lifecycle
Batches messages near the top of the stack. This reduces the work done on the IO thread and reduces overhead,
greatly increasing throughput for smaller message sizes (< 1k in test configurations). Also reduces the amount of
header data by having one header for each batch.
Conceptually, down messages are buffered then put in a wrapper message, so lower protocols only interact with the
wrapper. On the receiving end, the batch is unwrapped when it reaches this protocol and then forwarded to higher
protocols as individual messages in a loop.
- Since:
- 5.x
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic classprotected classprotected class -
Field Summary
FieldsModifier and TypeFieldDescriptionprotected longprotected Future<?> protected static BATCH.BatchHeaderintprotected Map<Address, BATCH.Buffer> protected final NullAddressprotected longprotected longprotected longprotected longprotected longprotected booleanprotected TimeSchedulerFields inherited from class org.jgroups.stack.Protocol
after_creation_hook, down_prot, ergonomics, id, local_addr, log, policies, stack, stats, up_prot -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptiondoubleAn event is to be sent down the stack.A message is sent down the stack.voidflush()protected voidhandleViewChange(List<Address> mbrs) voidinit()Called after a protocol has been created and before the protocol is started.voidvoidstart()This method is called on aJChannel.connect(String); starts work.voidvoidstop()Called on aJChannel.disconnect(); stops work (e.g.voidAn event was received from the protocol below.A single message was received.voidup(MessageBatch batch) Sends up a multiple messages in aMessageBatch.Methods inherited from class org.jgroups.stack.Protocol
accept, addPolicy, addr, addr, afterCreationHook, destroy, down, enableStats, getAddress, getComponents, getDownProtocol, getDownServices, getId, getIdsAbove, getLevel, getLog, getName, getPolicies, getProtocolStack, getSocketFactory, getThreadFactory, getTransport, getUpProtocol, getUpServices, getValue, isErgonomics, level, parse, policies, providedDownServices, providedUpServices, removePolicy, requiredDownServices, requiredUpServices, resetStatistics, setAddress, setDownProtocol, setErgonomics, setId, setLevel, setPolicies, setProtocolStack, setSocketFactory, setUpProtocol, setValue, statsEnabled, toString
-
Field Details
-
flush_interval
protected long flush_interval -
max_batch_size
public int max_batch_size -
num_msgs_sent
protected long num_msgs_sent -
num_ebs_sent
protected long num_ebs_sent -
num_ebs_sent_due_to_full_queue
protected long num_ebs_sent_due_to_full_queue -
num_ebs_sent_due_to_max_number_of_msgs
protected long num_ebs_sent_due_to_max_number_of_msgs -
num_ebs_sent_due_to_timeout
protected long num_ebs_sent_due_to_timeout -
nullAddress
-
timer
-
running
protected volatile boolean running -
flush_task
-
msgMap
-
HEADER
-
-
Constructor Details
-
BATCH
public BATCH()
-
-
Method Details
-
avgBatchSize
public double avgBatchSize() -
init
Description copied from class:ProtocolCalled after a protocol has been created and before the protocol is started. Attributes are already set. Other protocols are not yet connected and events cannot yet be sent. -
resetStats
public void resetStats()- Overrides:
resetStatsin classProtocol
-
down
Description copied from class:ProtocolAn event is to be sent down the stack. A protocol 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 protocol may need to add a header to it (or do nothing at all) before sending it down the stack usingdown_prot.down(). -
up
Description copied from class:ProtocolAn event was received from the protocol below. Usually the current protocol 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(). -
handleViewChange
-
down
Description copied from class:ProtocolA message is sent down the stack. Protocols may examine the message and do something (e.g. add a header) with it, before passing it down. -
up
Description copied from class:ProtocolA single message was received. Protocols may examine the message and do something (e.g. add a header) with it before passing it up. -
up
Description copied from class:ProtocolSends up a multiple messages in aMessageBatch. The sender of the batch is always the same, and so is the destination (null == multicast messages). Messages in a batch can be OOB messages, regular messages, or mixed messages, although the transport itself will create initial MessageBatches that contain only either OOB or regular messages.The default processing below sends messages up the stack individually, based on a matching criteria (calling
Protocol.accept(Message)), and - if true - callsProtocol.up(org.jgroups.Event)for that message and removes the message. If the batch is not empty, it is passed up, or else it is dropped.Subclasses should check if there are any messages destined for them (e.g. using
MessageBatch.iterator(Predicate)), then possibly remove and process them and finally pass the batch up to the next protocol. Protocols can also modify messages in place, e.g. ENCRYPT could decrypt all encrypted messages in the batch, not remove them, and pass the batch up when done. -
start
Description copied from class:ProtocolThis method is called on aJChannel.connect(String); starts work. Protocols are connected ready to receive events. Will be called from bottom to top. -
stop
public void stop()Description copied from class:ProtocolCalled on aJChannel.disconnect(); stops work (e.g. by closing multicast socket). Will be called from top to bottom. -
startFlushTask
public void startFlushTask() -
stopFlushTask
public void stopFlushTask() -
flush
public void flush()
-