[jira] [Comment Edited] (CASSANDRA-14192) netstats information mismatch between senders and receivers

2018-12-02 Thread Vincent White (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344515#comment-16344515
 ] 

Vincent White edited comment on CASSANDRA-14192 at 12/3/18 4:58 AM:


This is because we now use RangeAwareSSTableWriter to write out the incoming 
streams to disk. Its getFilename method returns just the keyspace/table rather 
than a complete filename (since it can write out more than one file during it's 
existence). This confuses the map of receivingFiles/sendingFiles in SessionInfo 
which is keyed on the output filename. 

I have been planning an update to netstats to correctly output this information 
again. I'll update this ticket when I have something useful.


was (Author: vincentwhite):
This is because we now use RangeAwareSSTableWriter to write out the incoming 
streams to disk. Its getFilename method returns just the keyspace/table rather 
than a complete filename (since it can write out more than one file during it's 
existence). This confuses the map of receivingFiles/sendingFiles in SessionInfo 
which is keyed on the output filename. 

I have been planning an update to netstats to correctly output this information 
again. I'll update this ticket when I have someone useful.

> netstats information mismatch between senders and receivers
> ---
>
> Key: CASSANDRA-14192
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14192
> Project: Cassandra
>  Issue Type: Bug
>  Components: Observability
>Reporter: Jonathan Ballet
>Assignee: Vincent White
>Priority: Minor
>
> When adding a new node to an existing cluster, the {{netstats}} command 
> called while the node is joining show different statistic values between the 
> node receiving the data and the nodes sending the data.
> Receiving node:
> {code}
> Mode: JOINING
> Bootstrap 0a599bf0-01c5-11e8-a256-8d847377f816
> /172.20.13.184
> /172.20.30.7
> Receiving 433 files, 36.64 GiB total. Already received 88 files, 4.6 
> GiB total
> [...]
> /172.20.40.128
> /172.20.16.45
> Receiving 405 files, 38.3 GiB total. Already received 86 files, 6.02 
> GiB total
> [...]
> /172.20.9.63
> Read Repair Statistics:
> Attempted: 0
> Mismatch (Blocking): 0
> Mismatch (Background): 0
> Pool NameActive   Pending  Completed   Dropped
> Large messages  n/a 0  0 0
> Small messages  n/a 0  11121 0
> Gossip messages n/a 0  32690 0
> {code}
> Sending node 1:
> {code}
> Mode: NORMAL
> Bootstrap 0a599bf0-01c5-11e8-a256-8d847377f816
> /172.20.21.19
> Sending 433 files, 36.64 GiB total. Already sent 433 files, 36.64 GiB 
> total
> [...]
> Read Repair Statistics:
> Attempted: 680832
> Mismatch (Blocking): 716
> Mismatch (Background): 279
> Pool NameActive   Pending  Completed   Dropped
> Large messages  n/a 2 123307 4
> Small messages  n/a 2  637010302   509
> Gossip messages n/a23 798851 11535
> {code}
> Sending node 2:
> {code}
> Mode: NORMAL
> Bootstrap 0a599bf0-01c5-11e8-a256-8d847377f816
> /172.20.21.19
> Sending 405 files, 38.3 GiB total. Already sent 405 files, 38.3 GiB 
> total
> [...]
> Read Repair Statistics:
> Attempted: 84967
> Mismatch (Blocking): 17568
> Mismatch (Background): 3078
> Pool NameActive   Pending  Completed   Dropped
> Large messages  n/a 2  17818 2
> Small messages  n/a 2  126082304   507
> Gossip messages n/a34 202810 11725
> {code}
> In this case, the join process is running since a while and the sending nodes 
> seem to say they sent everything already. This output stays the same for a 
> while though (maybe ~15% of the total joining time).
> However, the receiving node values stay like this once the sending nodes have 
> sent everything, until it goes from this state to the {{NORMAL}} state (so 
> there's visually no catching up from ~86 files to ~405 files for example, it 
> goes directly from the state showed above to {{NORMAL}})
> This makes tracking the progress of the join process a bit more difficult 
> than needed, because we need to compare and deduce the actual state from both 
> the receiving node values and the sending nodes values, which are both "not 
> correct" (sending nodes say everything has been sent but stays in this state 
> for a long time, receiving node says it still needs to download lot of 
> files/data before finishing.)



--
This 

[jira] [Commented] (CASSANDRA-14829) Make stop-server.bat wait for Cassandra to terminate

2018-12-02 Thread Dinesh Joshi (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706581#comment-16706581
 ] 

Dinesh Joshi commented on CASSANDRA-14829:
--

Hi [~georg], I apologize for the delay. I was traveling & on vacation so 
couldn't get around to this ticket. I have tested your change with Windows 10 
and it seems to be working as expected. I'm +1 on this change.

> Make stop-server.bat wait for Cassandra to terminate
> 
>
> Key: CASSANDRA-14829
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14829
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Packaging
> Environment: Windows 10
>Reporter: Georg Dietrich
>Assignee: Georg Dietrich
>Priority: Minor
>  Labels: easyfix, windows
> Fix For: 3.11.x, 4.x, 4.0.x
>
>
> While administering a single node Cassandra on Windows, I noticed that the 
> stop-server.bat script returns before the cassandra process has actually 
> terminated. For use cases like creating a script "shut down & create backup 
> of data directory without having to worry about open files, then restart", it 
> would be good to make stop-server.bat wait for Cassandra to terminate.
> All that is needed for that is to change in 
> apache-cassandra-3.11.3\bin\stop-server.bat "start /B powershell /file ..." 
> to "start /WAIT /B powershell /file ..." (additional /WAIT parameter).
> Does this sound reasonable?
> Here is the pull request: https://github.com/apache/cassandra/pull/287



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-14829) Make stop-server.bat wait for Cassandra to terminate

2018-12-02 Thread Dinesh Joshi (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706582#comment-16706582
 ] 

Dinesh Joshi commented on CASSANDRA-14829:
--

[~zznate] [~jjirsa] [~aweisberg] [~jasobrown] can any of you help committing 
this change?

> Make stop-server.bat wait for Cassandra to terminate
> 
>
> Key: CASSANDRA-14829
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14829
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Packaging
> Environment: Windows 10
>Reporter: Georg Dietrich
>Assignee: Georg Dietrich
>Priority: Minor
>  Labels: easyfix, windows
> Fix For: 3.11.x, 4.x, 4.0.x
>
>
> While administering a single node Cassandra on Windows, I noticed that the 
> stop-server.bat script returns before the cassandra process has actually 
> terminated. For use cases like creating a script "shut down & create backup 
> of data directory without having to worry about open files, then restart", it 
> would be good to make stop-server.bat wait for Cassandra to terminate.
> All that is needed for that is to change in 
> apache-cassandra-3.11.3\bin\stop-server.bat "start /B powershell /file ..." 
> to "start /WAIT /B powershell /file ..." (additional /WAIT parameter).
> Does this sound reasonable?
> Here is the pull request: https://github.com/apache/cassandra/pull/287



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-14829) Make stop-server.bat wait for Cassandra to terminate

2018-12-02 Thread Dinesh Joshi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Joshi updated CASSANDRA-14829:
-
Status: Ready to Commit  (was: Patch Available)

> Make stop-server.bat wait for Cassandra to terminate
> 
>
> Key: CASSANDRA-14829
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14829
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Packaging
> Environment: Windows 10
>Reporter: Georg Dietrich
>Assignee: Georg Dietrich
>Priority: Minor
>  Labels: easyfix, windows
> Fix For: 3.11.x, 4.x, 4.0.x
>
>
> While administering a single node Cassandra on Windows, I noticed that the 
> stop-server.bat script returns before the cassandra process has actually 
> terminated. For use cases like creating a script "shut down & create backup 
> of data directory without having to worry about open files, then restart", it 
> would be good to make stop-server.bat wait for Cassandra to terminate.
> All that is needed for that is to change in 
> apache-cassandra-3.11.3\bin\stop-server.bat "start /B powershell /file ..." 
> to "start /WAIT /B powershell /file ..." (additional /WAIT parameter).
> Does this sound reasonable?
> Here is the pull request: https://github.com/apache/cassandra/pull/287



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-14917) Nodetool netstats displays incorrect information on streaming

2018-12-02 Thread Yuki Morishita (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706575#comment-16706575
 ] 

Yuki Morishita commented on CASSANDRA-14917:


Are you using secondary indexes? Streaming is considered done after rebuilding 
index.

So you will see no progress in netstats even if you have 100% sent files.

I think we can improve this somehow.

> Nodetool netstats displays incorrect information on streaming
> -
>
> Key: CASSANDRA-14917
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14917
> Project: Cassandra
>  Issue Type: Bug
>  Components: Streaming and Messaging
>Reporter: Igor Zubchenok
>Assignee: Dinesh Joshi
>Priority: Minor
>
> nodetool netstats command displays 'Sending 0 files' and non-zero 'bytes 
> total' during node decommission.
> {code:java}
> Sending 0 files, 198933290919 bytes total. Already sent 0 files, 0 bytes total
> {code}
> Complete notetool netstats response
> {code:java}
> # nodetool netstats | grep -v 100%
> Mode: LEAVING
> Unbootstrap 67096090-f604-11e8--03532290668f
> /X.X.X.X
> Sending 8039 files, 174905861575 bytes total. Already sent 3147 
> files, 39883605552 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100884-big-Data.db
>  1866267759/8275615307 bytes(22%) sent to idx:0/5.9.54.111
> /X.X.X.X
> Sending 5475 files, 167399940563 bytes total. Already sent 2416 
> files, 49417386715 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bd8310f086b711e7b6cbfd84ea9f1f78/mc-459374-big-Data.db
>  10192112/17529144 bytes(58%) sent to idx:0/5.9.59.101
> /X.X.X.X
> Sending 5843 files, 181124719187 bytes total. Already sent 2613 
> files, 57001466824 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bd8310f086b711e7b6cbfd84ea9f1f78/mc-461873-big-Data.db
>  1439600/93308008 bytes(1%) sent to idx:0/46.4.31.97
> /X.X.X.X
> Sending 7303 files, 213976795121 bytes total. Already sent 1811 
> files, 28956350780 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100465-big-Data.db
>  3719051/37149976 bytes(10%) sent to idx:0/144.76.85.237
> /X.X.X.X
> Sending 7893 files, 204271020294 bytes total. Already sent 2397 
> files, 36086600359 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100197-big-Data.db
>  646314/8291439 bytes(7%) sent to idx:0/144.76.29.39
> /X.X.X.X
> Sending 0 files, 198933290919 bytes total. Already sent 0 files, 0 
> bytes total
> /X.X.X.X
> Sending 6159 files, 187102577561 bytes total. Already sent 1526 
> files, 26019708822 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100685-big-Data.db
>  52211410/67213497 bytes(77%) sent to idx:0/144.76.85.182
> /X.X.X.X
> Sending 6534 files, 193239644509 bytes total. Already sent 2367 
> files, 48105187871 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100884-big-Data.db
>  5907583715/10068538729 bytes(58%) sent to idx:0/5.9.48.222
> /X.X.X.X
> Sending 5923 files, 213438389441 bytes total. Already sent 1663 
> files, 32469866925 bytes total
> Read Repair Statistics:
> Attempted: 3537331
> Mismatch (Blocking): 2193
> Mismatch (Background): 4326
> Pool NameActive   Pending  Completed   Dropped
> Large messages  n/a18  87460   746
> Small messages  n/a 8 9837560424 12410
> Gossip messages n/a 87666199 84717
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Assigned] (CASSANDRA-14917) Nodetool netstats displays incorrect information on streaming

2018-12-02 Thread Dinesh Joshi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-14917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Joshi reassigned CASSANDRA-14917:


Assignee: Dinesh Joshi

> Nodetool netstats displays incorrect information on streaming
> -
>
> Key: CASSANDRA-14917
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14917
> Project: Cassandra
>  Issue Type: Bug
>  Components: Streaming and Messaging
>Reporter: Igor Zubchenok
>Assignee: Dinesh Joshi
>Priority: Minor
>
> nodetool netstats command displays 'Sending 0 files' and non-zero 'bytes 
> total' during node decommission.
> {code:java}
> Sending 0 files, 198933290919 bytes total. Already sent 0 files, 0 bytes total
> {code}
> Complete notetool netstats response
> {code:java}
> # nodetool netstats | grep -v 100%
> Mode: LEAVING
> Unbootstrap 67096090-f604-11e8--03532290668f
> /X.X.X.X
> Sending 8039 files, 174905861575 bytes total. Already sent 3147 
> files, 39883605552 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100884-big-Data.db
>  1866267759/8275615307 bytes(22%) sent to idx:0/5.9.54.111
> /X.X.X.X
> Sending 5475 files, 167399940563 bytes total. Already sent 2416 
> files, 49417386715 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bd8310f086b711e7b6cbfd84ea9f1f78/mc-459374-big-Data.db
>  10192112/17529144 bytes(58%) sent to idx:0/5.9.59.101
> /X.X.X.X
> Sending 5843 files, 181124719187 bytes total. Already sent 2613 
> files, 57001466824 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bd8310f086b711e7b6cbfd84ea9f1f78/mc-461873-big-Data.db
>  1439600/93308008 bytes(1%) sent to idx:0/46.4.31.97
> /X.X.X.X
> Sending 7303 files, 213976795121 bytes total. Already sent 1811 
> files, 28956350780 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100465-big-Data.db
>  3719051/37149976 bytes(10%) sent to idx:0/144.76.85.237
> /X.X.X.X
> Sending 7893 files, 204271020294 bytes total. Already sent 2397 
> files, 36086600359 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100197-big-Data.db
>  646314/8291439 bytes(7%) sent to idx:0/144.76.29.39
> /X.X.X.X
> Sending 0 files, 198933290919 bytes total. Already sent 0 files, 0 
> bytes total
> /X.X.X.X
> Sending 6159 files, 187102577561 bytes total. Already sent 1526 
> files, 26019708822 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100685-big-Data.db
>  52211410/67213497 bytes(77%) sent to idx:0/144.76.85.182
> /X.X.X.X
> Sending 6534 files, 193239644509 bytes total. Already sent 2367 
> files, 48105187871 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100884-big-Data.db
>  5907583715/10068538729 bytes(58%) sent to idx:0/5.9.48.222
> /X.X.X.X
> Sending 5923 files, 213438389441 bytes total. Already sent 1663 
> files, 32469866925 bytes total
> Read Repair Statistics:
> Attempted: 3537331
> Mismatch (Blocking): 2193
> Mismatch (Background): 4326
> Pool NameActive   Pending  Completed   Dropped
> Large messages  n/a18  87460   746
> Small messages  n/a 8 9837560424 12410
> Gossip messages n/a 87666199 84717
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Commented] (CASSANDRA-14917) Nodetool netstats displays incorrect information on streaming

2018-12-02 Thread Dinesh Joshi (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-14917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706555#comment-16706555
 ] 

Dinesh Joshi commented on CASSANDRA-14917:
--

Hi [~geagle] thanks for reporting this issue. Could you please add a detailed 
list of steps to reproduce this issue?

> Nodetool netstats displays incorrect information on streaming
> -
>
> Key: CASSANDRA-14917
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14917
> Project: Cassandra
>  Issue Type: Bug
>  Components: Streaming and Messaging
>Reporter: Igor Zubchenok
>Assignee: Dinesh Joshi
>Priority: Minor
>
> nodetool netstats command displays 'Sending 0 files' and non-zero 'bytes 
> total' during node decommission.
> {code:java}
> Sending 0 files, 198933290919 bytes total. Already sent 0 files, 0 bytes total
> {code}
> Complete notetool netstats response
> {code:java}
> # nodetool netstats | grep -v 100%
> Mode: LEAVING
> Unbootstrap 67096090-f604-11e8--03532290668f
> /X.X.X.X
> Sending 8039 files, 174905861575 bytes total. Already sent 3147 
> files, 39883605552 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100884-big-Data.db
>  1866267759/8275615307 bytes(22%) sent to idx:0/5.9.54.111
> /X.X.X.X
> Sending 5475 files, 167399940563 bytes total. Already sent 2416 
> files, 49417386715 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bd8310f086b711e7b6cbfd84ea9f1f78/mc-459374-big-Data.db
>  10192112/17529144 bytes(58%) sent to idx:0/5.9.59.101
> /X.X.X.X
> Sending 5843 files, 181124719187 bytes total. Already sent 2613 
> files, 57001466824 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bd8310f086b711e7b6cbfd84ea9f1f78/mc-461873-big-Data.db
>  1439600/93308008 bytes(1%) sent to idx:0/46.4.31.97
> /X.X.X.X
> Sending 7303 files, 213976795121 bytes total. Already sent 1811 
> files, 28956350780 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100465-big-Data.db
>  3719051/37149976 bytes(10%) sent to idx:0/144.76.85.237
> /X.X.X.X
> Sending 7893 files, 204271020294 bytes total. Already sent 2397 
> files, 36086600359 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100197-big-Data.db
>  646314/8291439 bytes(7%) sent to idx:0/144.76.29.39
> /X.X.X.X
> Sending 0 files, 198933290919 bytes total. Already sent 0 files, 0 
> bytes total
> /X.X.X.X
> Sending 6159 files, 187102577561 bytes total. Already sent 1526 
> files, 26019708822 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100685-big-Data.db
>  52211410/67213497 bytes(77%) sent to idx:0/144.76.85.182
> /X.X.X.X
> Sending 6534 files, 193239644509 bytes total. Already sent 2367 
> files, 48105187871 bytes total
> 
> /var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100884-big-Data.db
>  5907583715/10068538729 bytes(58%) sent to idx:0/5.9.48.222
> /X.X.X.X
> Sending 5923 files, 213438389441 bytes total. Already sent 1663 
> files, 32469866925 bytes total
> Read Repair Statistics:
> Attempted: 3537331
> Mismatch (Blocking): 2193
> Mismatch (Background): 4326
> Pool NameActive   Pending  Completed   Dropped
> Large messages  n/a18  87460   746
> Small messages  n/a 8 9837560424 12410
> Gossip messages n/a 87666199 84717
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Created] (CASSANDRA-14917) Nodetool netstats displays incorrect information on streaming

2018-12-02 Thread Igor Zubchenok (JIRA)
Igor Zubchenok created CASSANDRA-14917:
--

 Summary: Nodetool netstats displays incorrect information on 
streaming
 Key: CASSANDRA-14917
 URL: https://issues.apache.org/jira/browse/CASSANDRA-14917
 Project: Cassandra
  Issue Type: Bug
  Components: Streaming and Messaging
Reporter: Igor Zubchenok


nodetool netstats command displays 'Sending 0 files' and non-zero 'bytes total' 
during node decommission.
{code:java}
Sending 0 files, 198933290919 bytes total. Already sent 0 files, 0 bytes total
{code}
Complete notetool netstats response
{code:java}
# nodetool netstats | grep -v 100%
Mode: LEAVING
Unbootstrap 67096090-f604-11e8--03532290668f
/X.X.X.X
Sending 8039 files, 174905861575 bytes total. Already sent 3147 files, 
39883605552 bytes total

/var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100884-big-Data.db
 1866267759/8275615307 bytes(22%) sent to idx:0/5.9.54.111
/X.X.X.X
Sending 5475 files, 167399940563 bytes total. Already sent 2416 files, 
49417386715 bytes total

/var/lib/cassandra/data/app_tracks/tracks-bd8310f086b711e7b6cbfd84ea9f1f78/mc-459374-big-Data.db
 10192112/17529144 bytes(58%) sent to idx:0/5.9.59.101
/X.X.X.X
Sending 5843 files, 181124719187 bytes total. Already sent 2613 files, 
57001466824 bytes total

/var/lib/cassandra/data/app_tracks/tracks-bd8310f086b711e7b6cbfd84ea9f1f78/mc-461873-big-Data.db
 1439600/93308008 bytes(1%) sent to idx:0/46.4.31.97
/X.X.X.X
Sending 7303 files, 213976795121 bytes total. Already sent 1811 files, 
28956350780 bytes total

/var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100465-big-Data.db
 3719051/37149976 bytes(10%) sent to idx:0/144.76.85.237
/X.X.X.X
Sending 7893 files, 204271020294 bytes total. Already sent 2397 files, 
36086600359 bytes total

/var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100197-big-Data.db
 646314/8291439 bytes(7%) sent to idx:0/144.76.29.39
/X.X.X.X
Sending 0 files, 198933290919 bytes total. Already sent 0 files, 0 
bytes total
/X.X.X.X
Sending 6159 files, 187102577561 bytes total. Already sent 1526 files, 
26019708822 bytes total

/var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100685-big-Data.db
 52211410/67213497 bytes(77%) sent to idx:0/144.76.85.182
/X.X.X.X
Sending 6534 files, 193239644509 bytes total. Already sent 2367 files, 
48105187871 bytes total

/var/lib/cassandra/data/app_tracks/tracks-bfd4a21086b711e7b6cbfd84ea9f1f78/mc-100884-big-Data.db
 5907583715/10068538729 bytes(58%) sent to idx:0/5.9.48.222
/X.X.X.X
Sending 5923 files, 213438389441 bytes total. Already sent 1663 files, 
32469866925 bytes total
Read Repair Statistics:
Attempted: 3537331
Mismatch (Blocking): 2193
Mismatch (Background): 4326
Pool NameActive   Pending  Completed   Dropped
Large messages  n/a18  87460   746
Small messages  n/a 8 9837560424 12410
Gossip messages n/a 87666199 84717
{code}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org