Mailing-List: contact dev-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.apache.org
MIME-Version: 1.0
In-Reply-To: <D4D1D459.226D4%sparmar@threatmetrix.com>
References: <D4D1C169.226BD%sparmar@threatmetrix.com> <D4D1D459.226D4%sparmar@threatmetrix.com>
From: Ashwin Chandra Putta <ashwinchandrap@gmail.com>
Date: Tue, 21 Feb 2017 11:50:17 -0800
Message-ID: <CA+QE8bddHX1aNYPLrx-4xd_+BMC+xRjZJYgNfhVv2j_QhM=JZQ@mail.gmail.com>
Subject: Re: Occasional Out of order tuples when emitting from a thread
To: users@apex.apache.org
Cc: "dev@apex.apache.org" <dev@apex.apache.org>, Munagala Ramanath <ram@datatorrent.com>,
	Allan De Leon <adeleon@threatmetrix.com>, Tim Zhu <tzhu@threatmetrix.com>
Content-Type: multipart/alternative; boundary=001a11412778888ef005490fb011
archived-at: Tue, 21 Feb 2017 19:50:32 -0000

--001a11412778888ef005490fb011
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Sunil,

You can poll the queue in end window since process method in the input port
does not get called if there is no incoming tuple. However, end window is
called irrespective of there are incoming tuples or not.

Regards,
Ashwin.

On Tue, Feb 21, 2017 at 11:32 AM, Sunil Parmar <sparmar@threatmetrix.com>
wrote:

> Ram,
> Thanks for the prompt response. If we use the approach you suggested we=
=E2=80=99re
> dependent on main thread=E2=80=99s process call I.e. Tuples in the thread=
 safe
> queue gets only processed when main thread is processing incoming tuples.
> How can we explicitly call the process from polling of delay queue ?
>
> Just for reference here=E2=80=99s the sample code snippet for our operato=
r.
>
> public class MyOperator extends BaseOperator implements
>
>         Operator.ActivationListener<Context.OperatorContext> {
> =E2=80=A6..
>
> @InputPortFieldAnnotation
>
>     public transient DefaultInputPort<String> kafkaStreamInput =3D
>
>             new DefaultInputPort<String>() {
>
>         List<String> errors =3D new ArrayList<String>();
>
>         @Override
>
>         public void process(String consumerRecord) {
>
> //Code for normal tuple process
>
> //Code to poll thread safe queue
>
> }
>
> *=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94=E2=80=94=E2=80=94=E2=80=94**=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=
=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94*
> *From: *Munagala Ramanath <ram@datatorrent.com>
> *To: *users@apex.apache.org
> *CC: *"dev@apex.apache.org" <dev@apex.apache.org>, Allan De Leon <
> adeleon@threatmetrix.com>, Tim Zhu <tzhu@threatmetrix.com>
> *Subject: *Re: Occasional Out of order tuples when emitting from a thread
> *Date: *2017-02-21 10:08 (-0800)
> *List: *users@apex.apache.org
> <https://lists.apache.org/list.html?users@apex.apache.org>
>
> Please note that tuples should not be emitted by any thread other than th=
e
> main operator thread.
>
> A common pattern is to use a thread-safe queue and have worker threads
> enqueue
> tuples there; the main operator thread then pulls tuples from the queue a=
nd
> emits them.
>
> Ram
>
> _______________________________________________________
>
> Munagala V. Ramanath
>
> Software Engineer
>
> E: ram@datatorrent.com | M: (408) 331-5034 | Twitter: @UnknownRam
> www.datatorrent.com  |  apex.apache.org
>
>
> From: Sunil Parmar <sparmar@threatmetrix.com>
> Date: Tuesday, February 21, 2017 at 10:05 AM
> To: "users@apex.apache.org" <users@apex.apache.org>, "dev@apex.apache.org=
"
> <dev@apex.apache.org>
> Cc: Allan De Leon <adeleon@threatmetrix.com>, Tim Zhu <
> tzhu@threatmetrix.com>
> Subject: Occasional Out of order tuples when emitting from a thread
>
> Hi there,
> We have the following setup:
>
>    - we have a generic operator that=E2=80=99s processing tuples in its i=
nput port
>    - in the input port=E2=80=99s process method, we check for a condition=
, and:
>       - if the condition is met, the tuple is emitted to the next
>       operator right away (in the process method)
>       - Otherwise, if the condition is not met, we store the tuple  in
>       some cache and we use some threads that periodically check the cond=
ition to
>       become true. Once the condition is true, the threads call the emit =
method
>       on the stored tuples.
>
> With this setup, we occasionally encounter the following error:
> 2017-02-15 17:29:09,364 ERROR com.datatorrent.stram.engine.GenericNode:
> Catastrophic Error: Out of sequence BEGIN_WINDOW tuple 58a4046100003b7f o=
n
> port transformedJSON while expecting 58a4046100003b7e
>
> Is there a way to make the above work correctly?
> If not, can you recommend a better way of doing this?
> How can we ensure window assignment is done synchronously before emitting
> tuples ?
>
> Thanks very much in advance=E2=80=A6
> -allan
>


--=20

Regards,
Ashwin.

--001a11412778888ef005490fb011--