From user-return-14445-archive-asf-public=cust-asf.ponee.io@storm.apache.org Wed Jun 5 14:48:11 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id E3ADA18065D for ; Wed, 5 Jun 2019 16:48:10 +0200 (CEST) Received: (qmail 6119 invoked by uid 500); 5 Jun 2019 14:48:09 -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 6109 invoked by uid 99); 5 Jun 2019 14:48:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jun 2019 14:48:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 61D50C2DE0 for ; Wed, 5 Jun 2019 14:48:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.802 X-Spam-Level: * X-Spam-Status: No, score=1.802 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id QLLBp-S5fNMu for ; Wed, 5 Jun 2019 14:48:07 +0000 (UTC) Received: from mail-ot1-f52.google.com (mail-ot1-f52.google.com [209.85.210.52]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id D02705FBC9 for ; Wed, 5 Jun 2019 14:48:06 +0000 (UTC) Received: by mail-ot1-f52.google.com with SMTP id 107so942232otj.8 for ; Wed, 05 Jun 2019 07:48:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=x7z6nSSzbTMjBTRy4Q7FafvHfA1c0Y3TEqu0VcE7gZo=; b=p/JANG/P/+SrK7oLHyb96Qlp5ZHJqO+eEYHsqy6ZiMoXRzs1d5j8PXBFzVngGauiIS dAirip+4P+ZeqtHuSo5NBp1hSbJfZUSgJriIYX0fWpJir+ItZvkYxTqVSJ6BAaQ8ufCs 4fpT6mmm+HPKi+Zd+4XlaCBOt21DKzYUcFugWK8cgNvHtr61fY+6VKFKo5yhaKU7o4tN LTFw6EhMra7i8aJfE5bpQUnNVFWnZVUDMIUk5OUpXJTVqtJJ4tP5vmGBNqlDaOeP0rpA r1LAO+EybVDC9DfNL+oufFEEKUbNgYpj2+cPd9cjr8L+kq/FZd4gl1LW7g9Fv5+mJWOz bwpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=x7z6nSSzbTMjBTRy4Q7FafvHfA1c0Y3TEqu0VcE7gZo=; b=OUTvMRQuC5AIBzYacTQRqnzI9kfDMVNjzb6vEsCLNmMt316iB2GKZdsjxTSEt4VDKN AEsH126Z1Nr4UKsy4mCOZ5872/WxBCYgCeYFXQQ8iBHY0YKjvszYmi0AJecZrPK7CDNi YOMkFbnQWHzv5kLNNaVu2jXcf9zsMvwavITM1zLBn/ie7NhvMnJ1epB9TkLEDvPcFM/1 fW+AuSwAZ8hLtW0T5Hi5Oi8Hn1ImbEmRiVW3FpOEcICJJAX9G4wpG6Ir8mMTqYwZGl7S fOKxw7sMMgDctZ3slACn5B7rkximOWzFRmogSZgY1GBeVs3S466todadgiRhySyk28ss P9Tg== X-Gm-Message-State: APjAAAXmGHKWeX7dHStWusG3HLUWzx4fDeVT3aSAeNUR9VfniuAsk5/R pI/smbPdLoDAxksS64CD0pLRF5o0b5jUAR6VHG5GVg== X-Google-Smtp-Source: APXvYqy3LD6IoXLqTHSXiQvefT/EOTph0gvxn1eP9al0m+tPbgqdrouJyJW06SoQayqgE5qa9DRr1EGk4j1VvZB/zgc= X-Received: by 2002:a05:6830:208a:: with SMTP id y10mr3573601otq.293.1559746085761; Wed, 05 Jun 2019 07:48:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Stig_Rohde_D=C3=B8ssing?= Date: Wed, 5 Jun 2019 16:47:55 +0200 Message-ID: Subject: Re: Two simultaneous tuples from 2 incoming stream process order To: user@storm.apache.org Content-Type: multipart/alternative; boundary="00000000000061b536058a94afb2" --00000000000061b536058a94afb2 Content-Type: text/plain; charset="UTF-8" The "execute" method will never be called concurrently on the same bolt instance. In your topology, you will have some number of bolt C copies running (the task count for bolt C). Each copy will only receive one tuple in "execute" at a time. Any other tuples received while "execute" is running will be queued. Den ons. 5. jun. 2019 kl. 15.34 skrev : > Hi. > > It is possible the "execute" method of the bolt to be called in > "parallel"? For example we have 3 bolts A, B and C: > > topology.setBolt(BOLT_A_ID, new BoltA(), scaleFactor); > topology.setBolt(BOLT_B_ID, new BoltB(), scaleFactor); > topology.setBolt(BOLT_C_ID, new BoltC(), scaleFactor) > .allGrouping(BOLT_A_ID) > .fieldsGrouping(BOLT_B_ID, new Fields("some-key"); > > Bolts A and B produce tuples at the same time... i.e. their tuples will > arrive bolt C(same instance of this bolt) almost at the same time. Will > storm core postpone execution of the "second" tuple until "first" will be > processed? Or it will fire "execute" exactly when it will receive tuple(i.e > in parallel to current execution)? > > PS Storm version 1.1.0 > --00000000000061b536058a94afb2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The "execute" method will never be called c= oncurrently on the same bolt instance. In your topology, you will have some= number of bolt C copies running (the task count for bolt C). Each copy wil= l only receive one tuple in "execute" at a time. Any other tuples= received while "execute" is running will be queued.
<= br>
Den ons= . 5. jun. 2019 kl. 15.34 skrev <bogun.dmitriy@gmail.com>:
Hi.

It is possible = the "execute" method of the bolt to be called in "parallel&q= uot;? For example we have 3 bolts A, B and C:

topology.setBolt(BOLT_A_ID, new BoltA(), = scaleFactor);
topology.setBolt(BOLT_B_ID, new BoltB(), scaleFactor);
= topology.setBolt(BOLT_C_ID, new BoltC(), scaleFactor)
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 .allGrouping(BOLT_A_ID)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 .fieldsGr= ouping(BOLT_B_ID,=C2=A0new Fields("some-key");

Bolts A and B produce tuples at the same time... i.e= . their tuples will arrive bolt C(same instance of this bolt) almost at the= same time. Will storm core postpone execution of the "second" tu= ple until "first" will be processed? Or it will fire "execut= e" exactly when it will receive tuple(i.e in parallel to current execu= tion)?

<= div>PS Storm version 1.1.0
--00000000000061b536058a94afb2--