Return-Path: X-Original-To: apmail-samza-dev-archive@minotaur.apache.org Delivered-To: apmail-samza-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 15CBB18B83 for ; Wed, 6 Jan 2016 17:56:42 +0000 (UTC) Received: (qmail 55067 invoked by uid 500); 6 Jan 2016 17:56:41 -0000 Delivered-To: apmail-samza-dev-archive@samza.apache.org Received: (qmail 55001 invoked by uid 500); 6 Jan 2016 17:56:41 -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 54989 invoked by uid 99); 6 Jan 2016 17:56:41 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jan 2016 17:56:41 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 0062EC0628 for ; Wed, 6 Jan 2016 17:56:41 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.879 X-Spam-Level: ** X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 3e6i75TnW_DN for ; Wed, 6 Jan 2016 17:56:40 +0000 (UTC) Received: from mail-yk0-f173.google.com (mail-yk0-f173.google.com [209.85.160.173]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 49F07439F1 for ; Wed, 6 Jan 2016 17:56:40 +0000 (UTC) Received: by mail-yk0-f173.google.com with SMTP id x67so323764185ykd.2 for ; Wed, 06 Jan 2016 09:56:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=VkMx4IjKbLSpzTg60mxpNMNuxrX1Dl0yEQU1B7m9X8E=; b=cnOCIapKNlZPjqt6bZN9rYjVWBeQ7jC68rzMEbfYYlr1odVrIJCL9A9+VZCWlkf/w0 zNRAPPAlZ2Zt2mPU1ikfWyzz70m1Lx3H9tHCTZpO2Fxkk7xWI5ma0/KwPboJpd1Us8N/ gnzekloavFMG8vXZ6wbqRmauo+HwiymeUdJF6Ej7/405XtIHaY6Quv6DJL4vs/deBkce 2ZlgLS7yRM2mObT+JpW+T3KmqhCiiQv3+44lFa+XK1+Fe9FXiEHpqmtKhxngetLBFrI7 obk+Ct+SDmtfRnu1h/+STA0DN0V4N8A+D6PMIUbe1uOsbgS/Zf5CsMH++Ngy9W01fIfS /Fug== MIME-Version: 1.0 X-Received: by 10.129.99.69 with SMTP id x66mr7205810ywb.320.1452102999879; Wed, 06 Jan 2016 09:56:39 -0800 (PST) Received: by 10.37.14.69 with HTTP; Wed, 6 Jan 2016 09:56:39 -0800 (PST) Date: Wed, 6 Jan 2016 09:56:39 -0800 Message-ID: Subject: Question on zero downtime deployment of Samza jobs From: "Bae, Jae Hyeon" To: dev@samza.apache.org Content-Type: multipart/alternative; boundary=001a11473c5a7c38140528ae1364 --001a11473c5a7c38140528ae1364 Content-Type: text/plain; charset=UTF-8 Hi Samza devs and users I know this will be tricky in Samza because Samza Kafka consumer is not coordinated externally, but do you have any idea how to deploy samza jobs with zero downtime? Thank you Best, Jae --001a11473c5a7c38140528ae1364--