You could also run tcpdump to inspect the streams.
Dinesh
On Thursday, August 16, 2018, 1:11:47 PM PDT, Elliott Sims
wrote:
Since this is cross-node traffic, "nodetool netstats" during the high-traffic
period should give you a better idea of what's being sent.
On Thu, Aug 16, 2018
Since this is cross-node traffic, "nodetool netstats" during the
high-traffic period should give you a better idea of what's being sent.
On Thu, Aug 16, 2018 at 2:34 AM, Behnam B.Marandi <
behnam.b.mara...@gmail.com> wrote:
> In case of cronjobs, there is no jobs for that time period and I can
Hey folks,
As we start to get ready to feature freeze trunk for 4.0, it's going to be
important to get a lot of community feedback. This is going to be a big
release for a number of reasons.
* Virtual tables. Finally a nice way of querying for system metrics &
status
* Streaming optimizations
On Wed, Aug 15, 2018 at 3:23 AM kurt greaves wrote:
> Yep. It might require a full node replace depending on what data is lost from
> the system tables. In some cases you might be able to recover from partially
> lost system info, but it's not a sure thing.
Ugh, does it really just boil down
Dinesh, here is the ticket
https://issues.apache.org/jira/browse/CASSANDRA-14647
On Thu, Aug 16, 2018 at 10:13 AM dinesh.jo...@yahoo.com.INVALID
wrote:
> Vitali,
>
> It doesn't look like there is an existing Jira. It would be helpful if you
> could create one with as much information as
In case of cronjobs, there is no jobs for that time period and I can see
affect of jobs like backups and repairs but traffic that they cause is not
comparable. Like 800MB comparing to 2GB. And for this case it is all
outbound network on all 3 cluster nodes.
On Thu, Aug 16, 2018 at 5:16 PM
Since it is predictable, can you check the logs during that period? What do
they say? Do you have a cron running on those hosts? Do all the nodes
experience this issue?
Dinesh
On Thursday, August 16, 2018, 12:02:55 AM PDT, Behnam B.Marandi
wrote:
Actually I did. It seems this is a
Vitali,
It doesn't look like there is an existing Jira. It would be helpful if you
could create one with as much information as possible. Can you reduce this
issue to a short, repeatable set of steps that we can reproduce? That'll be
helpful to debug this problem.
Dinesh
On Wednesday,
Actually I did. It seems this is a cross node traffic from one node to port
7000 (storage_port) of the other node.
On Sun, Aug 12, 2018 at 2:44 PM Elliott Sims wrote:
> Since it's at a consistent time, maybe just look at it with iftop to see
> where the traffic's going and what port it's coming
