You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Eric Stevens <mi...@gmail.com> on 2014/11/01 15:08:24 UTC

Netstats > 100% streaming

We've been commissioning some new nodes on a 2.0.10 community edition
cluster, and we're seeing streams that look like they're shipping way more
data than they ought for individual files during bootstrap.


/var/lib/cassandra/data/xxxxx/yyyyy/xxxxx-yyyyy-jb-11748-Data.db
3756423/3715409 bytes(101%) sent to /1.2.3.4

/var/lib/cassandra/data/xxxxx/yyyyy/xxxxx-yyyyy-jb-11043-Data.db
584745/570432 bytes(102%) sent to /1.2.3.4
            /var/lib/cassandra/data/xxxxx/zzzzz/xxxxx-zzzzz-jb-525-Data.db
13020828/11141590 bytes(116%) sent to /1.2.3.4
            /var/lib/cassandra/data/xxxxx/wwwww/xxxxx-wwwww-jb-539-Data.db
1044124/51404 bytes(2031%) sent to /1.2.3.4
            /var/lib/cassandra/data/xxxxx/vvvvv/xxxxx-vvvvv-jb-546-Data.db
971447/22253 bytes(4365%) sent to /1.2.3.4

/var/lib/cassandra/data/xxxxx/yyyyy/xxxxx-yyyyy-jb-10404-Data.db
6225920/23215181 bytes(26%) sent to /1.2.3.4

Has anyone else seen something like this, and this something we should be
worried about?  I haven't been able to find any information about this
symptom.

-Eric

Re: Netstats > 100% streaming

Posted by Eric Stevens <mi...@gmail.com>.
Thanks Mark, that does seem like the right ticket.  Thanks for the info, I
wasn't successful finding that =)

On Mon, Nov 3, 2014 at 5:00 AM, Mark Reddy <ma...@gmail.com> wrote:

> HI Eric,
>
> It looks like you are running into CASSANDRA-7878
> <https://issues.apache.org/jira/browse/CASSANDRA-7878> which is fixed
> in 2.0.11 / 2.1.1
>
>
> Mark
>
> On 1 November 2014 14:08, Eric Stevens <mi...@gmail.com> wrote:
>
>> We've been commissioning some new nodes on a 2.0.10 community edition
>> cluster, and we're seeing streams that look like they're shipping way more
>> data than they ought for individual files during bootstrap.
>>
>>
>> /var/lib/cassandra/data/xxxxx/yyyyy/xxxxx-yyyyy-jb-11748-Data.db
>> 3756423/3715409 bytes(101%) sent to /1.2.3.4
>>
>> /var/lib/cassandra/data/xxxxx/yyyyy/xxxxx-yyyyy-jb-11043-Data.db
>> 584745/570432 bytes(102%) sent to /1.2.3.4
>>
>> /var/lib/cassandra/data/xxxxx/zzzzz/xxxxx-zzzzz-jb-525-Data.db
>> 13020828/11141590 bytes(116%) sent to /1.2.3.4
>>
>> /var/lib/cassandra/data/xxxxx/wwwww/xxxxx-wwwww-jb-539-Data.db
>> 1044124/51404 bytes(2031%) sent to /1.2.3.4
>>
>> /var/lib/cassandra/data/xxxxx/vvvvv/xxxxx-vvvvv-jb-546-Data.db 971447/22253
>> bytes(4365%) sent to /1.2.3.4
>>
>> /var/lib/cassandra/data/xxxxx/yyyyy/xxxxx-yyyyy-jb-10404-Data.db
>> 6225920/23215181 bytes(26%) sent to /1.2.3.4
>>
>> Has anyone else seen something like this, and this something we should be
>> worried about?  I haven't been able to find any information about this
>> symptom.
>>
>> -Eric
>>
>
>

Re: Netstats > 100% streaming

Posted by Mark Reddy <ma...@gmail.com>.
HI Eric,

It looks like you are running into CASSANDRA-7878
<https://issues.apache.org/jira/browse/CASSANDRA-7878> which is fixed
in 2.0.11 / 2.1.1


Mark

On 1 November 2014 14:08, Eric Stevens <mi...@gmail.com> wrote:

> We've been commissioning some new nodes on a 2.0.10 community edition
> cluster, and we're seeing streams that look like they're shipping way more
> data than they ought for individual files during bootstrap.
>
>
> /var/lib/cassandra/data/xxxxx/yyyyy/xxxxx-yyyyy-jb-11748-Data.db
> 3756423/3715409 bytes(101%) sent to /1.2.3.4
>
> /var/lib/cassandra/data/xxxxx/yyyyy/xxxxx-yyyyy-jb-11043-Data.db
> 584745/570432 bytes(102%) sent to /1.2.3.4
>             /var/lib/cassandra/data/xxxxx/zzzzz/xxxxx-zzzzz-jb-525-Data.db
> 13020828/11141590 bytes(116%) sent to /1.2.3.4
>             /var/lib/cassandra/data/xxxxx/wwwww/xxxxx-wwwww-jb-539-Data.db
> 1044124/51404 bytes(2031%) sent to /1.2.3.4
>             /var/lib/cassandra/data/xxxxx/vvvvv/xxxxx-vvvvv-jb-546-Data.db
> 971447/22253 bytes(4365%) sent to /1.2.3.4
>
> /var/lib/cassandra/data/xxxxx/yyyyy/xxxxx-yyyyy-jb-10404-Data.db
> 6225920/23215181 bytes(26%) sent to /1.2.3.4
>
> Has anyone else seen something like this, and this something we should be
> worried about?  I haven't been able to find any information about this
> symptom.
>
> -Eric
>