Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of jeremy.hanna1234@gmail.com
 designates 74.125.83.44 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: What causes dropped messages?
From: Jeremy Hanna <jeremy.hanna1234@gmail.com>
In-Reply-To: 
 <CAGjKECE3tZOOqCrKfRtei0OVq8Dhvd3imPse062U7SxO_=5_QQ@mail.gmail.com>
Date: Tue, 16 Aug 2011 10:05:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <48A360FC-FEA8-4674-970F-15C4831EEFF1@gmail.com>
References: 
 <CAGjKECE3tZOOqCrKfRtei0OVq8Dhvd3imPse062U7SxO_=5_QQ@mail.gmail.com>
To: user@cassandra.apache.org

http://wiki.apache.org/cassandra/FAQ#dropped_messages

As to what's causing them - look in the logs and it will do the =
equivalent of a nodetool tpstats right after the dropped messages =
messages.  That should give you a clue as to why there are dropped =
messages - which thread pools are backed up on that node.

On Aug 16, 2011, at 7:21 AM, David Boxenhorn wrote:

> How can I tell what's causing dropped messages?
>=20
> Is it just too much activity? I'm not getting any other, more specific =
messages, just these:=20
>=20
> WARN [ScheduledTasks:1] 2011-08-15 11:33:26,136 MessagingService.java =
(line 504) Dropped 1534 MUTATION messages in the last 5000ms
> WARN [ScheduledTasks:1] 2011-08-15 11:33:26,137 MessagingService.java =
(line 504) Dropped 58 READ_REPAIR messages in the last 5000ms
>=20