Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B99D4200D1E for ; Wed, 18 Oct 2017 17:58:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B800B160BEA; Wed, 18 Oct 2017 15:58:15 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0996E1609EE for ; Wed, 18 Oct 2017 17:58:14 +0200 (CEST) Received: (qmail 79345 invoked by uid 500); 18 Oct 2017 15:58:14 -0000 Mailing-List: contact dev-help@samza.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@samza.apache.org Delivered-To: mailing list dev@samza.apache.org Received: (qmail 79334 invoked by uid 99); 18 Oct 2017 15:58:14 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Oct 2017 15:58:14 +0000 Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 79FED1A012F for ; Wed, 18 Oct 2017 15:58:12 +0000 (UTC) Received: by mail-io0-f181.google.com with SMTP id 189so6733030iow.10 for ; Wed, 18 Oct 2017 08:58:12 -0700 (PDT) X-Gm-Message-State: AMCzsaUIcXCJgA+9poyzGU8ucg/enF0SkZqFeivz0YH4UrjbnLZOrKoO QjoQnjhxFVCvN1SgSaMEF3pp+pxETfwqAqogXm8= X-Google-Smtp-Source: AOwi7QAJfUzIu89HIZZxVjsj6S2OW9gV2WnR3Nge/2x674ELWVGhj9vXiHLeWkN5m0ISfISkpLiIDWJPk1h7y6y80os= X-Received: by 10.107.136.68 with SMTP id k65mr21859182iod.143.1508342291541; Wed, 18 Oct 2017 08:58:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.88.21 with HTTP; Wed, 18 Oct 2017 08:57:51 -0700 (PDT) In-Reply-To: References: From: Jake Maes Date: Wed, 18 Oct 2017 08:57:51 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Samza Standalone from multiple machines To: dev@samza.apache.org Content-Type: multipart/alternative; boundary="001a113ecd667cb567055bd44e4e" archived-at: Wed, 18 Oct 2017 15:58:15 -0000 --001a113ecd667cb567055bd44e4e Content-Type: text/plain; charset="UTF-8" Hey Giridhar, Boris would have more knowledge on this, but I'll offer a couple pointers: Running the "Hello Samza" application on multiple hosts should just be a matter of changing the "job.coordinator.zk.connect" property in the config to an external/shared ZK instance and starting more processors. The ZK Job Coordinator will automatically utilize more processors as they are started. However, if I remember correctly, the wikipedia stream is only a single partition and can't be processed by more than one processor, so you would probably want to change the input to a Kafka topic with at least as many partitions as your intended processors. More details about how standalone works can be found here: http://samza.apache.org/startup/preview/#flexible-deployment-model -Jake On Wed, Oct 18, 2017 at 4:06 AM, Giridhar Addepalli wrote: > Hi, > > i am new to Samza. > We are evaluating using Samza in Standalone mode. > > Was able to run "Hello Samza" using Zookeeper Deployment Model , on single > machine > http://samza.apache.org/learn/tutorials/latest/hello-samza- > high-level-zk.html > > We are wondering how to run Samza Job using Zookeeper Deployment Model > from multiple machines. > > Please point to relevant documentation or suggestions. > > Thanks, > Giridhar. > --001a113ecd667cb567055bd44e4e--