Hi, we're looking into Samza for doing real-time processing. We have couple questions w.r.t Samza functionality
1. One "must-have" requirement for us is zero/minimal downtime during deployment of Samza jobs. One approach that we're thinking of is to start a new instance of the same Samza job and make sure it's running before take down the running one. Is there any problem to this approach? If so, is there any suggestion for this problem as I'm unable to find anything related to this in documentation. 2. Is it possible to configure multiple Kafka topic partitions to a single task instance within a job? Since each task has its own JVM and some of the job that we have use a lot of memory, it would be very wasteful to run many instances of them Thanks much for your help! ------------------------------------------------------------------------------ Tony T Du Sr. Software Engineer - Dataminr I hear I forget. I see I remember. I do I understand. ------------------------------------------------------------------------------
