nothing in logs on the node that it was streaming from.
however, I think I found the issue on the other node in the C rack:
ERROR [STREAM-IN-/10.40.17.114] 2017-08-12 16:48:53,354
StreamSession.java:512 - [Stream #08957970-7f7e-11e7-b2a2-a31e21b877e5]
Streaming error occurred
org.apache.cassandra
Compaction is backed up that may be normal write load (because of the rack
imbalance), or it may be a secondary index build. Hard to say for sure.
nodetool compactionstats¹ if you¹re able to provide it. The jstack probably
not necessary, streaming is being marked as failed and it¹s turning itsel
Thanks for replying Jeff.
Responses below.
On Sat, Aug 12, 2017 at 8:33 PM Jeff Jirsa wrote:
> Answers inline
>
> --
> Jeff Jirsa
>
>
> > On Aug 12, 2017, at 2:58 PM, brian.spind...@gmail.com wrote:
> >
> > Hi folks, hopefully a quick one:
> >
> > We are running a 12 node cluster (2.1.15) in AW
Answers inline
--
Jeff Jirsa
> On Aug 12, 2017, at 2:58 PM, brian.spind...@gmail.com wrote:
>
> Hi folks, hopefully a quick one:
>
> We are running a 12 node cluster (2.1.15) in AWS with Ec2Snitch. It's all in
> one region but spread across 3 availability zones. It was nicely balanced
> w
Hi folks, hopefully a quick one:
We are running a 12 node cluster (2.1.15) in AWS with Ec2Snitch. It's all in
one region but spread across 3 availability zones. It was nicely balanced with
4 nodes in each.
But with a couple of failures and subsequent provisions to the wrong az we now
have a
Thanks for sending that out Patrick!
Really sad not to have a 2017 summit, but looking forward to 2018
summit(s).
On Fri, Aug 11, 2017 at 5:27 PM, Patrick McFadin wrote:
> Hello Cassandra Community,
>
> I know this is a hot topic so let me TL;DR for those of you looking for
> the short answe
