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 2E732102D2 for ; Sat, 1 Feb 2014 03:54:35 +0000 (UTC) Received: (qmail 81775 invoked by uid 500); 1 Feb 2014 03:54:34 -0000 Delivered-To: apmail-storm-user-archive@storm.apache.org Received: (qmail 81431 invoked by uid 500); 1 Feb 2014 03:54:22 -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 81421 invoked by uid 99); 1 Feb 2014 03:54:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Feb 2014 03:54:20 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of randolf.evered@lmco.com designates 192.31.106.12 as permitted sender) Received: from [192.31.106.12] (HELO mailfo01.lmco.com) (192.31.106.12) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Feb 2014 03:54:13 +0000 Received: from HDXHTPN8.us.lmco.com (hdxhtpn8.ems.lmco.com [158.188.83.9]) by mailfo01.lmco.com (8.14.5/8.14.5) with ESMTP id s113rqhB008910 for ; Sat, 1 Feb 2014 03:53:52 GMT Received: from HDXDSP51.us.lmco.com ([fe80::5c65:ed72:c3d9:280e]) by HDXHTPN8.us.lmco.com ([fe80::dcc0:27fd:804e:d443%15]) with mapi id 14.03.0174.001; Fri, 31 Jan 2014 20:53:52 -0700 From: "Evered, Randolf" To: "user@storm.incubator.apache.org" Subject: drpc.execute gives "execute failed: unknown result" Thread-Topic: drpc.execute gives "execute failed: unknown result" Thread-Index: Ac8fAKAOseajjxnpRsuqb3wDqnAQOQ== Date: Sat, 1 Feb 2014 03:49:38 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [158.188.95.9] Content-Type: multipart/alternative; boundary="_000_E3ABC1ECEC0B0E40AF6D4B8ED111011E232F1CFEHDXDSP51uslmcoc_" MIME-Version: 1.0 X-LM-Outbound: External 158.188.83.9 cntry=us g=7dffb9bc89b2e09d4eb1fc284f3e4a75 q=s113rqhB008910 m=1 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87,1.0.14,0.0.0000 definitions=2014-01-31_07:2014-01-31,2014-01-31,1970-01-01 signatures=0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_E3ABC1ECEC0B0E40AF6D4B8ED111011E232F1CFEHDXDSP51uslmcoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Nathan, We have a 1 node (one machine total) Storm cluster based on Storm 0.8.2. = We are using drpc.execute from mule to execute two different topologies (o= ne after another) with text and a POJO (serialized to a string). We're hav= ing an issue where Storm appears to be rarely and randomly dropping jobs af= ter we hit the timeout (conf.put(Config.TOPOLOGY_MESSAGE_TIMEOUT_SECS, 600)= ), where we'll get an exception on the client (mule) side producing this: org.apache.thrift7.TApplicationException: execute failed: unknown result at backtype.storm.generated.DistributedRPC$Client.recv_execute(Dist= ributedRPC.java:82) at backtype.storm.generated.DistributedRPC$Client.execute(Distribut= edRPC.java:61) at backtype.storm.utils.DRPCClient.execute(DRPCClient.java:54) Storm log analysis of the worker jvms indicate that the job completes just = fine, they just don't come back from the drpc.execute() until the timeout, = and then with the above mentioned non-useful exception . We are wondering if maybe trying to use Storm 0.9.0.1 would help with this?= Have you seen it before? We looked at the code for DistributedRPC and ca= n't imagine a message not having a result. Thank you, Randy --_000_E3ABC1ECEC0B0E40AF6D4B8ED111011E232F1CFEHDXDSP51uslmcoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Nathan,

 

We have a 1 node  (one machine total) Storm clu= ster based on Storm 0.8.2.  We are using  drpc.execute from mule = to execute two different topologies (one after another) with text and a POJ= O (serialized to a string).  We’re having an issue where Storm appears to be rarely and randomly dropping jobs after we hit t= he timeout (conf.put(Config.TOPOLOGY_MESSAGE_TIMEOUT_SECS, 600)), where we&= #8217;ll get an exception on the client (mule) side producing this:

 

org.apache.thrift7.TApplicationException: execute fa= iled: unknown result

        at backty= pe.storm.generated.DistributedRPC$Client.recv_execute(DistributedRPC.java:8= 2)

        at backty= pe.storm.generated.DistributedRPC$Client.execute(DistributedRPC.java:61)

        at backty= pe.storm.utils.DRPCClient.execute(DRPCClient.java:54)

 

Storm log analysis of the worker jvms indicate that = the job completes just fine, they just don’t come back from the drpc.= execute() until the timeout, and then with the above mentioned non-useful e= xception  .

 

We are wondering if maybe trying to use Storm 0.9.0.= 1 would help with this?  Have you seen it before?  We looked at t= he code for DistributedRPC and can’t imagine a message not having a r= esult.

 

Thank you,

Randy

 

--_000_E3ABC1ECEC0B0E40AF6D4B8ED111011E232F1CFEHDXDSP51uslmcoc_--