Hi, How many input streams does this task consume and how are they partitioned?
Garry -----Original Message----- From: Balusamy, Elangovan [mailto:elangovan.balus...@altisource.com] Sent: 02 September 2015 08:19 To: dev@samza.apache.org Cc: Chandra, Saurabh Subject: One task sending payload to multiple output streams Folks, We are running a multi-node Samza cluster with multiple partitions for each task. In one of the tasks, we would like to send output to two different tasks and the payload also is different. Below is the code that does it messageCollector.send(new OutgoingMessageEnvelope(output_stream_1, "this is for you")); messageCollector.send(new OutgoingMessageEnvelope(output_stream_2, "this is for the other guy")); output_stream_1 has 4 partitions output_stream_2 has 2 partitions We see that only 50% of the partitions are being used, the other 50% doesn't get any messages. output_stream_1 has messages only in 2 partitions and output_stream_2 has messages only in 1 partition. Samza version: 0.9.0 Kafka Version: 0.8.2.1 Thanks Elango *********************************************************************************************************************** This email message and any attachments are intended solely for the use of the addressee. If you are not the intended recipient, you are prohibited from reading, disclosing, reproducing, distributing, disseminating or otherwise using this transmission. If you have received this message in error, please promptly notify the sender by reply email and immediately delete this message from your system. This message and any attachments may contain information that is confidential, privileged or exempt from disclosure. Delivery of this message to any person other than the intended recipient is not intended to waive any right or privilege. Message transmission is not guaranteed to be secure or free of software viruses. *********************************************************************************************************************** ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4830 / Virus Database: 4365/10512 - Release Date: 08/25/15 Internal Virus Database is out of date.
