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 raymond.poling@citi.com
 designates 67.231.145.106 as permitted sender)
From: "Poling, Raymond " <raymond.poling@citi.com>
To: "'user@storm.incubator.apache.org'" <user@storm.incubator.apache.org>
Subject: Trouble with Acking After a Worker Fails
Thread-Topic: Trouble with Acking After a Worker Fails
Thread-Index: Ac9P9J3PcO07neg4RdOWLW8FPvbo1A==
Date: Fri, 4 Apr 2014 10:57:07 +0000
Message-ID: <FC0B269FDD2F7A47876B7AAAB6690BA72986C8F8@EXTXMB21.nam.nsroot.net>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_FC0B269FDD2F7A47876B7AAAB6690BA72986C8F8EXTXMB21namnsro_"
MIME-Version: 1.0

--_000_FC0B269FDD2F7A47876B7AAAB6690BA72986C8F8EXTXMB21namnsro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sometimes when we run a three node topology, if a worker fails and comes ba=
ck up, the entire topology will become sluggish, and messages will constant=
ly be marked as failed. After changing the logging, we can determine that t=
he topology is actually fully processing messages, however they are never b=
eing passed back to the acker to be acked. I've done searches to try and fi=
nd solutions (other than don't let the worker fail) to fix the issue, but h=
aven't found anything yet.


--_000_FC0B269FDD2F7A47876B7AAAB6690BA72986C8F8EXTXMB21namnsro_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Sometimes when we run a three node topology, if a wo=
rker fails and comes back up, the entire topology will become sluggish, and=
 messages will constantly be marked as failed. After changing the logging, =
we can determine that the topology
 is actually fully processing messages, however they are never being passed=
 back to the acker to be acked. I&#8217;ve done searches to try and find so=
lutions (other than don&#8217;t let the worker fail) to fix the issue, but =
haven&#8217;t found anything yet.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_FC0B269FDD2F7A47876B7AAAB6690BA72986C8F8EXTXMB21namnsro_--