Mailing-List: contact user-help@storm.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@storm.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of montedong@gmail.com designates
 209.85.216.41 as permitted sender)
MIME-Version: 1.0
Date: Fri, 4 Apr 2014 13:01:13 -0500
Message-ID: 
 <CAAUsAoTUzcczHRJOGor1upPLyh4n5yGKyy7L7RLDvheSB9WS=w@mail.gmail.com>
Subject: Tuple queuing mechanism in storm
From: Dong Mo <montedong@gmail.com>
To: user@storm.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a11c2c262afb2de04f63b4d3e

--001a11c2c262afb2de04f63b4d3e
Content-Type: text/plain; charset=ISO-8859-1

Dear list,

I would like to know how tuple queuing works in Storm.

What is the semantic of emit() exactly when it returns?

Does a returned emit mean that the tuple is successfully delivered to the
destination or that a tuple is delivered to this bolt's local sending queue
waiting for delivery over the network?

Is that a blocking function or it has no reliable delivery guarantee at all?

More generally, how does storm's receiving and sending queue mechanism
works?

Say I have a boltA emitting words very quickly and it is connected to
another boltB which do super complicated encryption on the words and thus
is very slow. In this scenario, where does the "queue" get built up and
where does the tuple drop happen? Will boltA get blocked also because the
blocking emit? Or boltA will just emit tuple with reliably delivery in
sense of TCP and the receiving queue of BoltB will get overflowed?

Thanks
-Mo

--001a11c2c262afb2de04f63b4d3e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear list,<div><br></div><div>I would like to know how tup=
le queuing works in Storm.</div><div><br></div><div><div style=3D"font-fami=
ly:arial,sans-serif;font-size:13.63636302947998px">What is the semantic of =
emit() exactly when it returns?</div>
<div style=3D"font-family:arial,sans-serif;font-size:13.63636302947998px"><=
br></div><div style=3D"font-family:arial,sans-serif;font-size:13.6363630294=
7998px">Does a returned emit mean that the tuple is successfully delivered =
to the destination or that a tuple is delivered to this bolt&#39;s local se=
nding queue waiting for delivery over the network?</div>
<div style=3D"font-family:arial,sans-serif;font-size:13.63636302947998px"><=
br></div><div style=3D"font-family:arial,sans-serif;font-size:13.6363630294=
7998px">Is that a blocking function or it has no reliable delivery guarante=
e at all?</div>
<div style=3D"font-family:arial,sans-serif;font-size:13.63636302947998px"><=
br></div><div style=3D"font-family:arial,sans-serif;font-size:13.6363630294=
7998px">More generally, how does storm&#39;s receiving and sending queue me=
chanism works?</div>
<div style=3D"font-family:arial,sans-serif;font-size:13.63636302947998px"><=
br></div><div style=3D"font-family:arial,sans-serif;font-size:13.6363630294=
7998px">Say I have a boltA emitting words very quickly and it is connected =
to another boltB which do super complicated encryption on the words and thu=
s is very slow. In this scenario, where does the &quot;queue&quot; get buil=
t up and where does the tuple drop happen? Will boltA get blocked also beca=
use the blocking emit? Or boltA will just emit tuple with reliably delivery=
 in sense of TCP and the receiving queue of BoltB will get overflowed?</div=
>
</div><div style=3D"font-family:arial,sans-serif;font-size:13.6363630294799=
8px"><br></div><div style=3D"font-family:arial,sans-serif;font-size:13.6363=
6302947998px">Thanks</div><div style=3D"font-family:arial,sans-serif;font-s=
ize:13.63636302947998px">
-Mo</div><div style=3D"font-family:arial,sans-serif;font-size:13.6363630294=
7998px"><br></div></div>

--001a11c2c262afb2de04f63b4d3e--