Return-Path: X-Original-To: apmail-storm-user-archive@minotaur.apache.org Delivered-To: apmail-storm-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3104410325 for ; Tue, 1 Apr 2014 14:25:10 +0000 (UTC) Received: (qmail 31481 invoked by uid 500); 1 Apr 2014 14:25:09 -0000 Delivered-To: apmail-storm-user-archive@storm.apache.org Received: (qmail 31152 invoked by uid 500); 1 Apr 2014 14:25:07 -0000 Mailing-List: contact user-help@storm.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.incubator.apache.org Delivered-To: mailing list user@storm.incubator.apache.org Received: (qmail 31131 invoked by uid 99); 1 Apr 2014 14:25:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2014 14:25:05 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of anujsays@gmail.com designates 209.85.212.175 as permitted sender) Received: from [209.85.212.175] (HELO mail-wi0-f175.google.com) (209.85.212.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2014 14:25:01 +0000 Received: by mail-wi0-f175.google.com with SMTP id cc10so5265753wib.2 for ; Tue, 01 Apr 2014 07:24:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=tk9YgbAafV/TujpYyS8yRVNxwiTsEheSdHK7N+zgQR0=; b=zW/mulBNMsWRwhnC6rXUbLCsVSq97M9qq47Cd2yzlsNCBpVIpYOx5nWFxVbLgy9+Wm cWLZKQgZ6L0DGv8PG1gS6vkVpMJxTyU7Lzi9Z+HEUlz8PyVK69qtr/vlT4ySS2gyz/pO 3CnKQ1TNah1K8SVFrgfOiMkhcOZzxfm1XkurcscouEldUQLRQ5+d/LsD+FKNqoS2taFm fljgn7o3Bd24Ai/QY/ixvTyICZW3x20eRbxp5bJzjcUSSMwqaJU1w8QHrw/Y4WMh3i2n /skiQDmSzkg/Pm4apMFP6Wra9A79TXb6F9b78sN+DIzmhynGrbZ/gU/zd2INDfZIuk/Y fKYQ== MIME-Version: 1.0 X-Received: by 10.180.101.40 with SMTP id fd8mr20312215wib.1.1396362280513; Tue, 01 Apr 2014 07:24:40 -0700 (PDT) Received: by 10.217.11.201 with HTTP; Tue, 1 Apr 2014 07:24:40 -0700 (PDT) In-Reply-To: References: Date: Tue, 1 Apr 2014 19:54:40 +0530 Message-ID: Subject: Re: Whole topology restarts when a worker crash From: Anuj Kumar To: user@storm.incubator.apache.org Content-Type: multipart/alternative; boundary=f46d041826c6b538bf04f5fbed94 X-Virus-Checked: Checked by ClamAV on apache.org --f46d041826c6b538bf04f5fbed94 Content-Type: text/plain; charset=ISO-8859-1 Hi Quentin, What is your Storm version? I am running on 0.8.2. Regards, Anuj On Tue, Apr 1, 2014 at 7:26 PM, Quentin de G. wrote: > Hey Anuj, thanks for your answer. > Unfortunately that's not what I'm seeing in Storm UI. > > I have 2 machines running the workers, with one worker / machine. > When I kill a worker (kill -9 pid), even the tasks that were not running > on this worker are restarted (uptime of all tasks reset). > > > Maybe I'm doing something wrong in my topology, or some config parameters > are wrong. > > Thanks, > > Quentin > > > > > On Tue, Apr 1, 2014 at 3:26 PM, Anuj Kumar wrote: > >> Hi Quentin, >> >> If the worker crashes only the associated executor threads running the >> tasks are restarted. Not the entire topology. >> >> Regards, >> Anuj >> >> >> On Tue, Apr 1, 2014 at 6:44 PM, Quentin de G. wrote: >> >>> Hello everyone, >>> >>> It seems that when one worker crashes, the whole topology is restarted. >>> Is there a way to tune that, like only restarting tasks that were bound >>> to this worker? >>> >>> Thanks. >>> -- >>> Quentin de Grandmaison >>> >>> / LinkedInprofile / Profil >>> Viadeo Mon CV >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >> > > > -- > Quentin de Grandmaison > > / LinkedInprofile / Profil > Viadeo Mon CV > > > > > > > > > > > > > > > > > --f46d041826c6b538bf04f5fbed94 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Quentin,

What is your Storm version?= I am running on 0.8.2.

Regards,
Anuj


On Tue, Apr 1, 2014 at 7:26 PM, Quentin = de G. <quentin.de.gr@gmail.com> wrote:
Hey Anuj, thanks for your answer.
= Unfortunately that's not what I'm seeing in Storm UI.

=
I have 2 machines running the workers, with one worker / machine.
When I kill a worker (kill -9 pid), even the tasks that were not= running on this worker are restarted (uptime of all tasks reset).

<= br>
Maybe I'm doing something wrong in my topology, or some config= parameters are wrong.

Thanks,

Quentin

=



On Tue, Apr 1, 2014 at 3:26 PM, Anuj Kumar <anujsays@gmail.com>= wrote:
Hi Quent= in,

If the worker crashes only the associated executor t= hreads running the tasks are restarted. Not the entire topology.

Regards,
Anuj


On Tue, Apr 1= , 2014 at 6:44 PM, Quentin de G. <quentin.de.gr@gmail.com> wrote:
Hello everyone,

It seems that when one worker crashes, = the whole topology is restarted.
Is there a way to tune that, like only restarting tasks that were bou= nd to this worker?

Thanks.
--
=09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09
=09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09
=09
=09
Quenti= n de Grandmaison
/ LinkedIn= profile / Profil Viadeo Mon CV


















--
=09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09
=09 =09 =09 =09 =09 =09 =09 =09 =09 =09 =09
=09
=09
Quenti= n de Grandmaison
/ LinkedIn= profile / Profil Viadeo Mon CV















--f46d041826c6b538bf04f5fbed94--