Re: Scaling samza jobs in standalone deployment

app.id is used to identify an instance of your application. Each application consumes all partitions for all topics. With unique app.id , what you really have is two Samza jobs running simultaneously. Sounds to me like what you’re expecting is a single Samza job

Scaling samza jobs in standalone deployment

Hello Team, I am testing scaling of Samza jobs in standalone deployment model. Jobs are deployed in Kubernetes with zookeeper as job coordinator. The input Kafka topic has two partitions and I am running two Samza instances. The configuration supplied to both instances are identical except app.id,