Class WorkPullingProducerController
- java.lang.Object
-
- org.apache.pekko.actor.typed.delivery.WorkPullingProducerController
-
public class WorkPullingProducerController extends java.lang.ObjectWork pulling is a pattern where several worker actors pull tasks in their own pace from a shared work manager instead of that the manager pushes work to the workers blindly without knowing their individual capacity and current availability.The
WorkPullingProducerControllercan be used together withConsumerControllerto implement the work pulling pattern.One important property is that the order of the messages should not matter, because each message is routed randomly to one of the workers with demand. In other words, two subsequent messages may be routed to two different workers and processed independent of each other.
A worker actor (consumer) and its
ConsumerControlleris dynamically registered to theWorkPullingProducerControllervia apekko.actor.typed.receptionist.ServiceKey. It will register itself to the *pekko.actor.typed.receptionist.Receptionist, and theWorkPullingProducerControllersubscribes to the same key to find active workers. In this way workers can be dynamically added or removed from any node in the cluster.The work manager (producer) actor will start the flow by sending a
WorkPullingProducerController.Startmessage to theWorkPullingProducerController. TheActorRefin theStartmessage is typically constructed as a message adapter to map theWorkPullingProducerController.RequestNextto the protocol of the producer actor.The
WorkPullingProducerControllersendsRequestNextto the producer, which is then allowed to send one message to theWorkPullingProducerControllervia thesendNextToin theRequestNext. Thereafter the producer will receive a newRequestNextwhen it's allowed to send one more message. It will send a newRequestNextwhen there are demand from any worker. It's possible that all workers with demand are deregistered after theRequestNextis sent and before the actual messages is sent to theWorkPullingProducerController. In that case the message is buffered and will be delivered when a new worker is registered or when there is new demand.The producer and
WorkPullingProducerControlleractors are supposed to be local so that these messages are fast and not lost. This is enforced by a runtime check.Many unconfirmed messages can be in flight between the
WorkPullingProducerControllerand eachConsumerController. The flow control is driven by the consumer side, which means that theWorkPullingProducerControllerwill not send faster than the demand requested by the workers.Lost messages are detected, resent and deduplicated if needed. This is also driven by the consumer side, which means that the
WorkPullingProducerControllerwill not push resends unless requested by theConsumerController.If a worker crashes or is stopped gracefully the unconfirmed messages for that worker will be routed to other workers by the
WorkPullingProducerController. This may result in that some messages may be processed more than once, by different workers.Until sent messages have been confirmed the
WorkPullingProducerControllerkeeps them in memory to be able to resend them. If the JVM of theWorkPullingProducerControllercrashes those unconfirmed messages are lost. To make sure the messages can be delivered also in that scenario theWorkPullingProducerControllercan be used with aDurableProducerQueue. Then the unconfirmed messages are stored in a durable way so that they can be redelivered when the producer is started again. An implementation of theDurableProducerQueueis provided byEventSourcedProducerQueueinpekko-persistence-typed.Instead of using
tellwith thesendNextToin theRequestNextthe producer can usecontext.askwith theaskNextToin theRequestNext. The difference is that a reply is sent back when the message has been handled. If aDurableProducerQueueis used then the reply is sent when the message has been stored successfully, but it might not have been processed by the consumer yet. Otherwise the reply is sent after the consumer has processed and confirmed the message.It's also possible to use the
WorkPullingProducerControllerandConsumerControllerwithout resending lost messages, but the flow control is still used. This can for example be useful when both consumer and producer are know to be located in the same localActorSystem. This can be more efficient since messages don't have to be kept in memory in theProducerControlleruntil they have been confirmed, but the drawback is that lost messages will not be delivered. See configurationonly-flow-controlof theConsumerController.The
producerIdis used in logging and included as MDC entry with key"producerId". It's propagated to theConsumerControllerand is useful for correlating log messages. It can be anyStringbut it's recommended to use a unique identifier of representing the producer.If the
DurableProducerQueueis defined it is created as a child actor of theWorkPullingProducerControlleractor.ProducerControlleractors are created for each registered worker. Those child actors use the same dispatcher as the parentWorkPullingProducerController.
-
-
Nested Class Summary
Nested Classes Modifier and Type Class Description static interfaceWorkPullingProducerController.Command<A>static classWorkPullingProducerController.GetWorkerStats<A>Retrieve information about registered workers.static classWorkPullingProducerController.GetWorkerStats$static classWorkPullingProducerController.MessageWithConfirmation<A>For sending confirmation message back to the producer when the message has been fully delivered, processed, and confirmed by the consumer.static classWorkPullingProducerController.MessageWithConfirmation$static classWorkPullingProducerController.RequestNext<A>TheWorkPullingProducerControllersendsRequestNextto the producer when it is allowed to send one message via thesendNextTooraskNextTo.static classWorkPullingProducerController.RequestNext$static classWorkPullingProducerController.Settingsstatic classWorkPullingProducerController.Settings$static classWorkPullingProducerController.Start<A>Initial message from the producer actor.static classWorkPullingProducerController.Start$static classWorkPullingProducerController.WorkerStatsstatic classWorkPullingProducerController.WorkerStats$
-
Constructor Summary
Constructors Constructor Description WorkPullingProducerController()
-
Method Summary
All Methods Static Methods Concrete Methods Modifier and Type Method Description static <A> Behavior<WorkPullingProducerController.Command<A>>apply(java.lang.Class<A> messageClass, java.lang.String producerId, ServiceKey<ConsumerController.Command<A>> workerServiceKey, java.util.Optional<Behavior<DurableProducerQueue.Command<A>>> durableQueueBehavior, WorkPullingProducerController.Settings settings)Java APIstatic <A> Behavior<WorkPullingProducerController.Command<A>>apply(java.lang.String producerId, ServiceKey<ConsumerController.Command<A>> workerServiceKey, scala.Option<Behavior<DurableProducerQueue.Command<A>>> durableQueueBehavior, WorkPullingProducerController.Settings settings, scala.reflect.ClassTag<A> evidence$2)static <A> Behavior<WorkPullingProducerController.Command<A>>apply(java.lang.String producerId, ServiceKey<ConsumerController.Command<A>> workerServiceKey, scala.Option<Behavior<DurableProducerQueue.Command<A>>> durableQueueBehavior, scala.reflect.ClassTag<A> evidence$1)static <A> Behavior<WorkPullingProducerController.Command<A>>create(java.lang.Class<A> messageClass, java.lang.String producerId, ServiceKey<ConsumerController.Command<A>> workerServiceKey, java.util.Optional<Behavior<DurableProducerQueue.Command<A>>> durableQueueBehavior)Java APIstatic <A> java.lang.Class<WorkPullingProducerController.RequestNext<A>>requestNextClass()Java API: The genericClasstype forWorkPullingProducerController.RequestNextthat can be used when creating amessageAdapterforClass.>
-
-
-
Method Detail
-
requestNextClass
public static <A> java.lang.Class<WorkPullingProducerController.RequestNext<A>> requestNextClass()
Java API: The genericClasstype forWorkPullingProducerController.RequestNextthat can be used when creating amessageAdapterforClass.>
-
apply
public static <A> Behavior<WorkPullingProducerController.Command<A>> apply(java.lang.String producerId, ServiceKey<ConsumerController.Command<A>> workerServiceKey, scala.Option<Behavior<DurableProducerQueue.Command<A>>> durableQueueBehavior, scala.reflect.ClassTag<A> evidence$1)
-
apply
public static <A> Behavior<WorkPullingProducerController.Command<A>> apply(java.lang.String producerId, ServiceKey<ConsumerController.Command<A>> workerServiceKey, scala.Option<Behavior<DurableProducerQueue.Command<A>>> durableQueueBehavior, WorkPullingProducerController.Settings settings, scala.reflect.ClassTag<A> evidence$2)
-
create
public static <A> Behavior<WorkPullingProducerController.Command<A>> create(java.lang.Class<A> messageClass, java.lang.String producerId, ServiceKey<ConsumerController.Command<A>> workerServiceKey, java.util.Optional<Behavior<DurableProducerQueue.Command<A>>> durableQueueBehavior)
Java API
-
apply
public static <A> Behavior<WorkPullingProducerController.Command<A>> apply(java.lang.Class<A> messageClass, java.lang.String producerId, ServiceKey<ConsumerController.Command<A>> workerServiceKey, java.util.Optional<Behavior<DurableProducerQueue.Command<A>>> durableQueueBehavior, WorkPullingProducerController.Settings settings)
Java API
-
-