your
Node is under heavy load.
From: Ney, Richard [mailto:richard@aspect.com]
Sent: Tuesday, January 03, 2017 2:58 PM
To: user@cassandra.apache.org
Subject: Re: Trying to find cause of exception
Johnny,
Would these WARN cause the read issues I’m seeing
WARN [GossipTasks:1] 2017-01-03 03:27
;
Date: Monday, January 2, 2017 at 1:28 PM
To: "user@cassandra.apache.org"
Subject: Re: Trying to find cause of exception
Richard,
From looking at the stack trace in your Cassandra logs, you might be hitting a
variation of this bug:
https://issues.apache.org/jira/browse/CASSANDRA-
Miller
Reply-To: "user@cassandra.apache.org"
Date: Monday, January 2, 2017 at 1:28 PM
To: "user@cassandra.apache.org"
Subject: Re: Trying to find cause of exception
Richard,
From looking at the stack trace in your Cassandra logs, you might be hitting a
variation of this bug:
h
RESEARCH & DEVELOPMENT
> +1 (978) 848.6640 WORK
> +1 (916) 846.2353 MOBILE
> UNITED STATES
> richard@aspect.com <mailto:richard@aspect.com>
> aspect.com <http://www.aspect.com/>
>
>
>
> From: Amit Singh F <mailto:amit.f.si...@ericsson.com>>
>
richard@aspect.com<mailto:richard@aspect.com>
aspect.com<http://www.aspect.com/>
[mailSigLogo-rev.jpg]
From: Amit Singh F
Reply-To: "user@cassandra.apache.org"
Date: Monday, January 2, 2017 at 4:34 AM
To: "user@cassandra.apache.org"
Subject: RE: Trying to find cause o
msgs. Are you able to connect?
Regards
Amit
From: Ney, Richard [mailto:richard@aspect.com]
Sent: Monday, January 02, 2017 3:30 PM
To: user@cassandra.apache.org
Subject: Trying to find cause of exception
My development team has been trying to track down the cause of this Read
timeout (30
My development team has been trying to track down the cause of this Read
timeout (30 seconds or more at times) exception below. We’re running a 2 data
center deployment with 3 nodes in each data center. Our tables are setup with
replication factor = 2 and we have 16G dedicated to the heap with t
