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 70ED8200B7E for ; Tue, 6 Sep 2016 21:08:21 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6F775160ACB; Tue, 6 Sep 2016 19:08:21 +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 1E526160AA9 for ; Tue, 6 Sep 2016 21:08:19 +0200 (CEST) Received: (qmail 13233 invoked by uid 500); 6 Sep 2016 19:08:19 -0000 Mailing-List: contact user-help@storm.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.apache.org Delivered-To: mailing list user@storm.apache.org Received: (qmail 13223 invoked by uid 99); 6 Sep 2016 19:08:18 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Sep 2016 19:08:18 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 88978180502 for ; Tue, 6 Sep 2016 19:08:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.298 X-Spam-Level: * X-Spam-Status: No, score=1.298 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gobalto-com.20150623.gappssmtp.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id xisZ287NpGwU for ; Tue, 6 Sep 2016 19:08:15 +0000 (UTC) Received: from mail-yb0-f176.google.com (mail-yb0-f176.google.com [209.85.213.176]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 800065F242 for ; Tue, 6 Sep 2016 19:08:14 +0000 (UTC) Received: by mail-yb0-f176.google.com with SMTP id 125so95861841ybe.3 for ; Tue, 06 Sep 2016 12:08:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gobalto-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=4b5fB70G1HbvIjM4I+X0uE3rf9C7lx0VSYNaMWwYuOk=; b=ZCa1JIQFPR1/vnpm5HrQ06v3X8XUtTzI7nQ+hM80xgLFmJNBoMYwamR2JbU062dOdH HwPyIVpfx7y+j7YKdeV1vA5BKVk/rFgA1IFhG8qKZ9nstP8QdvQnFDabPxoRB9hr+It5 RaITyEbmCZWVhKv6sICwFu43I3xHYmp4wIiokljhTP8ZVRxYTTgkvtyzutqkV5xUJPKw HIUSagMhD0bHJGF/H+O7LgwA8WELLbnHFRVktTKkeFh9bxddHJBvXmICqhpaAUu4/U6a 0YHQ9YFgS0I3tMKEJPlvSu66QABlUtcAj6/8VG6p2NsDgPtF2nsX6UHdr2NlxL/0GSRm zFaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=4b5fB70G1HbvIjM4I+X0uE3rf9C7lx0VSYNaMWwYuOk=; b=ejG60SVB4KETzK9iGBHctI6giThbjqebrCJj2V9j/FQu1LLcTkbSrp3tQdrAU8HKTW MtZhMGcrO1nZ7LS4NjrzL1MdafKQZX2S7WGFTZT43kTVllx/melJGHfrg2ie0VbfNPys 15BXfth1qjhSbL1iK9ofZJIEPGkoMfJvcOgIHSE9BbnZklOR05+/39vSKi4WaLdXN0+l hPNuy3BGLa55k/OMAfYV1X5tJ9Og++XF8yTUEDxNVY9dxZ0drb0dVUKG3i9aeFeBiWqb Mh77I3YW0xYKtz984U2P6EhE3ox3zXponH122dIJwAhcHVpAY2rcZU/Miln3bRsTCtlp MBLA== X-Gm-Message-State: AE9vXwMAo00yCMDpcs6hD44xJK/ybf8kjLX7KcofY7vg7jxDj8rNyeIKWQoNZFilahKD8Wj2vPSt0cWjDpUr7SKM X-Received: by 10.36.116.131 with SMTP id o125mr383780itc.7.1473188893240; Tue, 06 Sep 2016 12:08:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.95.129 with HTTP; Tue, 6 Sep 2016 12:08:12 -0700 (PDT) In-Reply-To: References: <5DCE24EC-0E48-4AA1-A700-F2AB48248304@gmail.com> From: Joaquin Menchaca Date: Tue, 6 Sep 2016 12:08:12 -0700 Message-ID: Subject: Re: [SURVEY] What version of Storm are you using? To: user@storm.apache.org Content-Type: multipart/alternative; boundary=001a114abf70ab4892053bdb842a archived-at: Tue, 06 Sep 2016 19:08:21 -0000 --001a114abf70ab4892053bdb842a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable update, we are using 0.10.0 now, but exploring 1.0.2. currently working on logviwer issue. On Tue, Sep 6, 2016 at 9:05 AM, Renjie Liu wrote: > Most of our clusters are running on 0.10.0, and we are trying 1.0.1 > > On Sun, Aug 21, 2016 at 12:04 AM Andrea Gazzarini > wrote: > >> 1.0.1 for a pilot (hopefully soon in production) >> >> Andrea >> >> On 20 Aug 2016 17:52, "Rahul Chugh" wrote: >> >>> We are using 1.0.1 in production. >>> >>> >>> >>> - Rahul >>> >>> >>> >>> *From: *saiprasad mishra >>> *Reply-To: *"user@storm.apache.org" >>> *Date: *Saturday, August 20, 2016 at 1:28 AM >>> *To: *"user@storm.apache.org" >>> *Subject: *Re: [SURVEY] What version of Storm are you using? >>> >>> >>> >>> @Walmart E-Commerce >>> >>> >>> >>> Upgraded one of our cluster from 0.10 to 1.0.1 a month back and running >>> successfully without any issues. Its worth all the time spent on the >>> upgrade as the new features are awesome for debugging and for everybody= . >>> >>> >>> >>> Another critical cluster is already upgraded from 0.9.4 to 1.0.1 and >>> will be live soon in matter of days. >>> >>> >>> >>> Upgrade was very straight forward as most of the changes are in pom.xml >>> and we mainly use the storm-kafka spout with kafka 0.9.X client libs an= d >>> kafka 0.9.X brokers. >>> >>> >>> >>> >>> >>> 1) Only blocker was log4j2 change as mentioned above. We were using >>> scribe-logback for logging. >>> >>> So we ended up creating our own scribe log4j2 custom appender which was >>> anyway needed for any type of applications within our team. >>> >>> >>> >>> >>> >>> 2) One issue which we are facing right now is killing the topology from >>> cli some times does not kill the worker in 1.0.1 though the UI says >>> KILLED.Though there is a workaround for this(like clearing nimbus state= by >>> hand) but still looking for a clean solution(considering to go to 1.0.2= for >>> this plus other stability fixes it has). I saw couple of JIRAs but not = sure >>> whether those made it 1.0.2 >>> >>> >>> >>> Overall +1 for storm 1.0.x upgrade. Lot of useful features which makes >>> everybody's life easier especially ops team. >>> >>> >>> >>> Regards >>> >>> Sai >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> On Thu, Aug 18, 2016 at 9:17 PM, Zhechao Ma >>> wrote: >>> >>> We upgrade from 0.9.5 to 1.0.1 recently. >>> >>> >>> >>> 2016-08-18 11:26 GMT+08:00 P. Taylor Goetz : >>> >>> +1 >>> >>> >>> >>> Any and all feedback is always welcome. >>> >>> >>> >>> -Taylor >>> >>> >>> On Aug 17, 2016, at 9:22 PM, Jungtaek Lim wrote: >>> >>> off-topic: >>> >>> Andrew and Erik, please feel free to post the issue to dev@ whenever >>> you meet the issue from streamparse, storm-mesos, and etc. which might = be >>> cause of upstream so that Storm dev. community can help if possible. >>> >>> >>> >>> 2016=EB=85=84 8=EC=9B=94 18=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 10:= 07, Andrew Montalenti =EB=8B=98=EC=9D=B4 =EC=9E=91=EC= =84=B1: >>> >>> Erik, re: this issue, "blocked by us dealing with mysterious Storm >>> Worker process heartbeat failures", do you have any topo's @ Groupon us= ing >>> ShellSpout (multi-lang)? >>> >>> If so, the patch/resolution in STORM-1928 (released in 1.0.2, see JIRA >>> for details) may be helpful. >>> >>> >>> >>> On Aug 17, 2016 6:07 PM, "Jungtaek Lim" wrote: >>> >>> Side note for users waiting stable version of 1.x: 1.0.2 is worth to tr= y >>> out since it's well tested, and fixes various critical bugs users met. >>> >>> >>> >>> - Jungtaek Lim (HeartSaVioR) >>> >>> >>> >>> 2016=EB=85=84 8=EC=9B=94 18=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 6:5= 8, Erik Weathers =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84= =B1: >>> >>> Groupon is using 0.9.6. >>> >>> >>> >>> Switching to 0.10.0 or 1.0+ will take us more time largely because of >>> the "logback to log4j 2" change in 0.10. We have a bunch of internal t= eams >>> using a library for logging which is based on logback, and it's definit= ely >>> going to be herding cats to get them to upgrade their topologies. >>> >>> >>> >>> We are also responsible for the storm-mesos framework, which we will >>> hopefully come back to adding support for 1.0+ next month on. Spendin= g >>> time on that is currently blocked by us dealing with mysterious Storm >>> Worker process heartbeat failures. >>> >>> >>> >>> - Erik >>> >>> >>> >>> On Wed, Aug 17, 2016 at 2:47 PM, Joaquin Menchaca >>> wrote: >>> >>> 0.10.0 >>> >>> >>> >>> >>> >>> >>> >> -- > Liu, Renjie > Software Engineer, MVAD > --=20 =E6=98=AF=E6=95=85=E5=8B=9D=E5=85=B5=E5=85=88=E5=8B=9D=E8=80=8C=E5=BE=8C=E6= =B1=82=E6=88=B0=EF=BC=8C=E6=95=97=E5=85=B5=E5=85=88=E6=88=B0=E8=80=8C=E5=BE= =8C=E6=B1=82=E5=8B=9D=E3=80=82 --001a114abf70ab4892053bdb842a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
update, we are using 0.10.0 now, but exploring 1.0.2.=
currently working on logviwer issue.

On Tue, Sep 6, 2016 at 9:05 AM, Renj= ie Liu <liurenjie2008@gmail.com> wrote:
Most of our clusters are running on 0.= 10.0, and we are trying 1.0.1
=
On Sun, Aug 21, 2016 at 12:= 04 AM Andrea Gazzarini <gxsubs@gmail.com> wrote:

1.0.1 for a pilot (hopefully soon in production)

Andrea


On 20 Aug 2016 17= :52, "Rahul Chugh" <rahul.chugh@fixstream.com> wrote:

We are using 1.0.1 in production.

=C2=A0

- Rahul

=C2=A0

F= rom: saiprasad mishra <saiprasadmishr= a@gmail.com>
Reply-To: "user@storm.apache.org" <user@storm.apache.org>
Date: Saturday, August 20, 2016 at 1:28 AM
To: "user@storm.apache.org" <user@storm.apache.org>
Subject: Re: [SURVEY] What version of Storm are you using?=

=C2=A0

@Walmart E-Commerce

=C2=A0

Upgraded one of our cluster from 0.10 to 1.0.1 a mon= th back and running successfully without any issues. Its worth all the time= spent on the upgrade as the new features are awesome for debugging and for= everybody.

=C2=A0

Another critical cluster is already upgraded from 0.= 9.4 to 1.0.1 and will be live soon in matter of days.

=C2=A0

Upgrade was very straight forward as most of the cha= nges are in pom.xml and we mainly use the storm-kafka spout with kafka 0.9.= X client libs and kafka 0.9.X brokers.

=C2=A0

=C2=A0

1) Only blocker was log4j2 change as mentioned above= . We were using scribe-logback for logging.

So we ended up creating our own scribe log4j2 custom= appender which was anyway needed for any type of applications within our t= eam.

=C2=A0

=C2=A0

2) One issue which we are facing right now is killin= g the topology from cli some times does not kill the worker in 1.0.1 though= the UI says KILLED.Though there is a workaround for this(like clearing nim= bus state by hand) but still looking for a clean solution(considering to go to 1.0.2 for this plus other stabil= ity fixes it has). I saw couple of JIRAs but not sure whether those made it= 1.0.2

=C2=A0

Overall +1 for storm 1.0.x upgrade. Lot of useful fe= atures which makes everybody's life easier especially ops team.<= u>

=C2=A0

Regards

Sai

=C2=A0

=C2=A0

=C2=A0

=C2=A0

On Thu, Aug 18, 2016 at 9:17 PM, Zhechao Ma <mazhechaomaill= ist@gmail.com> wrote:

We upgrade from 0.9.5 to 1.0.1 recently.

=C2=A0

2016-08-18 11:26 GMT+08:00 P. Taylor Goetz <ptgoetz@gmail.com>= :

+1

=C2=A0

Any and all feedback is always welcome.

=C2=A0

-Taylor<= /span>


On Aug 17, 2016, at 9:22 PM, Jungtaek Lim <kabhwan@gmail.com> wrote:

off-topic:

Andrew and Erik, please feel free to post the issue = to dev@ whenever you meet the issue from streamparse, storm-mesos, and etc.= which might be cause of upstream so that=C2=A0Storm dev. community can hel= p if possible.

=C2=A0

2016=EB=85=84 8=EC=9B=94 18=EC=9D=BC (= =EB=AA=A9) =EC=98=A4=EC=A0=84 10:07, Andrew Montalenti <andrew@parsely.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:

Erik, re: this issue, "blocked by us dealing with mysterious Storm = Worker process heartbeat failures", do you have any topo's @ Group= on using ShellSpout (multi-lang)?

If so, the patch/resolution in STORM-1928 (released in 1.0.2, see JIRA f= or details) may be helpful.

=C2=A0

On Aug 17, 2016 6:07 PM, "Jungtaek Lim" &l= t;kabhwan@gmail.com<= /a>> wrote:

Side note for users waiting stable version of 1.x: 1= .0.2 is worth to try out since it's well tested, and fixes various crit= ical bugs users met.

=C2=A0

- Jungtaek Lim (HeartSaVioR)

=C2=A0

Groupon is using 0.9.6.

=C2=A0

Switching to 0.10.0 or 1.0+ will take us more time l= argely because of the "logback to log4j 2" change in 0.10.=C2=A0 = We have a bunch of internal teams using a library for logging which is base= d on logback, and it's definitely going to be herding cats to get them to upgrade their topologies.

=C2=A0

We are also responsible for the storm-mesos framewor= k, which we will hopefully come back to adding support for 1.0+ next month = on. =C2=A0 Spending time on that is currently blocked by us dealing with my= sterious Storm Worker process heartbeat failures.

=C2=A0

- Erik

=C2=A0

On Wed, Aug 17, 2016 at 2:47 PM, Joaquin Menchaca &l= t;jmenchaca@goba= lto.com> wrote:

0.10.0

=C2=A0

=C2=A0

=C2=A0

--
Liu, Renjie
Software Engineer, MVAD



--
<= div>

=E6=98=AF=E6=95=85=E5=8B=9D=E5=85=B5=E5=85=88=E5=8B= =9D=E8=80=8C=E5=BE=8C=E6=B1=82=E6=88=B0=EF=BC=8C=E6=95=97=E5=85=B5=E5=85=88= =E6=88=B0=E8=80=8C=E5=BE=8C=E6=B1=82=E5=8B=9D=E3=80=82=
--001a114abf70ab4892053bdb842a--