Re: Custom ordering when using async

Hi, Xiaochuan, Please refer to the document here: https://samza.apache.org/learn/tutorials/0.13/samza-async-user-guide.html As stated, by default, when task.max.concurrency=1, in-order processing within a task is guaranteed, no matter whether you implement StreamTask or AsyncStreamTask. The engin

Re: Custom ordering when using async

Hi Jagadish, This is a rather late reply but I don't think I understand of the effect of changing job.container.thread.pool.size config in the synchronous case very well. Suppose I have an input topic partitioned by memberID processed by a synchronous job. Does increasing container thread pool siz

Re: Custom ordering when using async

Hi XiaoChuan, Are you setting task.max.concurrency > 1 that allows multiple messages in-flight? (The "keyed executor pool" is only meaningful with that scenario) Also, Have you tried increasing your *job.container.thread.pool.size *config and setting it to the number of tasks in the container? Gi

Re: Custom ordering when using async

Hi, XiaoChuan, For your questions: 1. By "keyed single thread executor pool", it means something like a map from a key to a single thread executor, like Map where each Executor is a Executors.*newSingleThreadExecutor