Re: cassandro nodes restarts

2018-07-25 Thread Jeff Jirsa 
It’s a warning, but probably not causing you problems

A 20kB batch is a hint that your batches are larger than Cassandra expects, but 
the 5k limit for that logger was somewhat arbitrary, and I would be shocked if 
20kB batches were a problem unless you were already close to tipping your 
cluster

If I were you I’d disable that warning (or set it much higher).

-- 
Jeff Jirsa


> On Jul 25, 2018, at 7:32 PM, R1 J1  wrote:
> 
> cassandro nodes restarts
> 
> 
> 
> we see errors typically like these
> 
> 
> WARN  [Native-Transport-Requests-3] 2018-07-25 20:51:38,520 
> BatchStatement.java:301 - Batch for "keyspace.table"
>  is of size 19.386KiB, exceeding specified threshold of 5.000KiB by 14.386KiB.
> 
> 
> Regards
> R1J1

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

cassandro nodes restarts

2018-07-25 Thread R1 J1 
cassandro nodes restarts



we see errors typically like these


WARN  [Native-Transport-Requests-3] 2018-07-25 20:51:38,520
BatchStatement.java:301 - Batch for "keyspace.table"
 is of size 19.386KiB, exceeding specified threshold of 5.000KiB by
14.386KiB.


Regards
R1J1

Re: Reaper 1.2 released

2018-07-25 Thread Mick Semb Wever 


Feel free to file issues at 
https://github.com/thelastpickle/cassandra-reaper/issues
or chat with us at https://gitter.im/thelastpickle/cassandra-reaper

regards,
Mick



On Thu, 26 Jul 2018, at 06:18, Abdul Patel wrote:
> Was abke start it but unable to start any repair manually it says
> POST/repair_run
> Unit conflits with exiting in clustername
> 
> On Wednesday, July 25, 2018, Abdul Patel  wrote:
> 
> > Ignore , alter and create permission were missing ..will msg if i actually
> > see an showstopper
> >
> > On Wednesday, July 25, 2018, Abdul Patel  wrote:
> >
> >> I am trying to uograde to 1.2.2 version of reaper the instance isnt
> >> starting and giving error that unable to create table snapshot ..do we need
> >> to create it under reaper-db?
> >>
> >> On Wednesday, July 25, 2018, Steinmaurer, Thomas <
> >> thomas.steinmau...@dynatrace.com> wrote:
> >>
> >>> Jon,
> >>>
> >>>
> >>>
> >>> eager trying it out.  Just FYI. Followed the installation
> >>> instructions on http://cassandra-reaper.io/docs/download/install/
> >>> Debian-based.
> >>>
> >>>
> >>>
> >>> 1) Importing the key results in:
> >>>
> >>>
> >>>
> >>> XXX:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
> >>> 2895100917357435
> >>>
> >>> Executing: /tmp/tmp.tP0KAKG6iT/gpg.1.sh --keyserver
> >>>
> >>> keyserver.ubuntu.com
> >>>
> >>> --recv-keys
> >>>
> >>> 2895100917357435
> >>>
> >>> gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
> >>>
> >>> ?: [fd 4]: read error: Connection reset by peer
> >>>
> >>> gpgkeys: HTTP fetch error 7: couldn't connect: eof
> >>>
> >>> gpg: no valid OpenPGP data found.
> >>>
> >>> gpg: Total number processed: 0
> >>>
> >>> gpg: keyserver communications error: keyserver unreachable
> >>>
> >>> gpg: keyserver communications error: public key not found
> >>>
> >>> gpg: keyserver receive failed: public key not found
> >>>
> >>>
> >>>
> >>> I had to change the keyserver URL then the import worked:
> >>>
> >>>
> >>>
> >>> XXX:~$ sudo apt-key adv --keyserver *hkp://keyserver.ubuntu.com:80
> >>> * --recv-keys 2895100917357435
> >>>
> >>> Executing: /tmp/tmp.JwPNeUkm6x/gpg.1.sh --keyserver
> >>>
> >>> hkp://keyserver.ubuntu.com:80
> >>>
> >>> --recv-keys
> >>>
> >>> 2895100917357435
> >>>
> >>> gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
> >>>
> >>> gpg: key 17357435: public key "TLP Reaper packages <
> >>> rea...@thelastpickle.com>" imported
> >>>
> >>> gpg: Total number processed: 1
> >>>
> >>> gpg:   imported: 1  (RSA: 1)
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> 2) Running apt-get update fails with:
> >>>
> >>>
> >>>
> >>> XXX:~$ sudo apt-get update
> >>>
> >>> Ign:1 https://dl.bintray.com/thelastpickle/reaper-deb wheezy InRelease
> >>>
> >>> Ign:2 https://dl.bintray.com/thelastpickle/reaper-deb wheezy Release
> >>>
> >>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> >>> Packages
> >>>
> >>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> >>> Packages
> >>>
> >>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> >>> Packages
> >>>
> >>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en_US
> >>>
> >>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en
> >>>
> >>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> >>> Packages
> >>>
> >>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> >>> Packages
> >>>
> >>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> >>> Packages
> >>>
> >>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en_US
> >>>
> >>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en
> >>>
> >>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> >>> Packages
> >>>
> >>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> >>> Packages
> >>>
> >>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> >>> Packages
> >>>
> >>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en_US
> >>>
> >>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en
> >>>
> >>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> >>> Packages
> >>>
> >>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> >>> Packages
> >>>
> >>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> >>> Packages
> >>>
> >>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en_US
> >>>
> >>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> >>> Translation-en
> >>>
> >>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> >>> Packages
> >>>
> >>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb

Re: Reaper 1.2 released

2018-07-25 Thread Abdul Patel 
Was abke start it but unable to start any repair manually it says
POST/repair_run
Unit conflits with exiting in clustername

On Wednesday, July 25, 2018, Abdul Patel  wrote:

> Ignore , alter and create permission were missing ..will msg if i actually
> see an showstopper
>
> On Wednesday, July 25, 2018, Abdul Patel  wrote:
>
>> I am trying to uograde to 1.2.2 version of reaper the instance isnt
>> starting and giving error that unable to create table snapshot ..do we need
>> to create it under reaper-db?
>>
>> On Wednesday, July 25, 2018, Steinmaurer, Thomas <
>> thomas.steinmau...@dynatrace.com> wrote:
>>
>>> Jon,
>>>
>>>
>>>
>>> eager trying it out.  Just FYI. Followed the installation
>>> instructions on http://cassandra-reaper.io/docs/download/install/
>>> Debian-based.
>>>
>>>
>>>
>>> 1) Importing the key results in:
>>>
>>>
>>>
>>> XXX:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
>>> 2895100917357435
>>>
>>> Executing: /tmp/tmp.tP0KAKG6iT/gpg.1.sh --keyserver
>>>
>>> keyserver.ubuntu.com
>>>
>>> --recv-keys
>>>
>>> 2895100917357435
>>>
>>> gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
>>>
>>> ?: [fd 4]: read error: Connection reset by peer
>>>
>>> gpgkeys: HTTP fetch error 7: couldn't connect: eof
>>>
>>> gpg: no valid OpenPGP data found.
>>>
>>> gpg: Total number processed: 0
>>>
>>> gpg: keyserver communications error: keyserver unreachable
>>>
>>> gpg: keyserver communications error: public key not found
>>>
>>> gpg: keyserver receive failed: public key not found
>>>
>>>
>>>
>>> I had to change the keyserver URL then the import worked:
>>>
>>>
>>>
>>> XXX:~$ sudo apt-key adv --keyserver *hkp://keyserver.ubuntu.com:80
>>> * --recv-keys 2895100917357435
>>>
>>> Executing: /tmp/tmp.JwPNeUkm6x/gpg.1.sh --keyserver
>>>
>>> hkp://keyserver.ubuntu.com:80
>>>
>>> --recv-keys
>>>
>>> 2895100917357435
>>>
>>> gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
>>>
>>> gpg: key 17357435: public key "TLP Reaper packages <
>>> rea...@thelastpickle.com>" imported
>>>
>>> gpg: Total number processed: 1
>>>
>>> gpg:   imported: 1  (RSA: 1)
>>>
>>>
>>>
>>>
>>>
>>> 2) Running apt-get update fails with:
>>>
>>>
>>>
>>> XXX:~$ sudo apt-get update
>>>
>>> Ign:1 https://dl.bintray.com/thelastpickle/reaper-deb wheezy InRelease
>>>
>>> Ign:2 https://dl.bintray.com/thelastpickle/reaper-deb wheezy Release
>>>
>>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>>> Packages
>>>
>>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>>> Packages
>>>
>>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
>>> Packages
>>>
>>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>>> Translation-en_US
>>>
>>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>>> Translation-en
>>>
>>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>>> Packages
>>>
>>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>>> Packages
>>>
>>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
>>> Packages
>>>
>>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>>> Translation-en_US
>>>
>>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>>> Translation-en
>>>
>>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>>> Packages
>>>
>>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>>> Packages
>>>
>>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
>>> Packages
>>>
>>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>>> Translation-en_US
>>>
>>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>>> Translation-en
>>>
>>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>>> Packages
>>>
>>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>>> Packages
>>>
>>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
>>> Packages
>>>
>>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>>> Translation-en_US
>>>
>>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>>> Translation-en
>>>
>>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>>> Packages
>>>
>>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>>> Packages
>>>
>>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
>>> Packages
>>>
>>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>>> Translation-en_US
>>>
>>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>>> Translation-en
>>>
>>> Err:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>>> Packages
>>>
>>>   Received HTTP code 403 from proxy after CONNECT
>>>
>>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>>> Packages

Re: Reaper 1.2 released

2018-07-25 Thread Abdul Patel 
Ignore , alter and create permission were missing ..will msg if i actually
see an showstopper

On Wednesday, July 25, 2018, Abdul Patel  wrote:

> I am trying to uograde to 1.2.2 version of reaper the instance isnt
> starting and giving error that unable to create table snapshot ..do we need
> to create it under reaper-db?
>
> On Wednesday, July 25, 2018, Steinmaurer, Thomas <
> thomas.steinmau...@dynatrace.com> wrote:
>
>> Jon,
>>
>>
>>
>> eager trying it out.  Just FYI. Followed the installation instructions
>> on http://cassandra-reaper.io/docs/download/install/ Debian-based.
>>
>>
>>
>> 1) Importing the key results in:
>>
>>
>>
>> XXX:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
>> 2895100917357435
>>
>> Executing: /tmp/tmp.tP0KAKG6iT/gpg.1.sh --keyserver
>>
>> keyserver.ubuntu.com
>>
>> --recv-keys
>>
>> 2895100917357435
>>
>> gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
>>
>> ?: [fd 4]: read error: Connection reset by peer
>>
>> gpgkeys: HTTP fetch error 7: couldn't connect: eof
>>
>> gpg: no valid OpenPGP data found.
>>
>> gpg: Total number processed: 0
>>
>> gpg: keyserver communications error: keyserver unreachable
>>
>> gpg: keyserver communications error: public key not found
>>
>> gpg: keyserver receive failed: public key not found
>>
>>
>>
>> I had to change the keyserver URL then the import worked:
>>
>>
>>
>> XXX:~$ sudo apt-key adv --keyserver *hkp://keyserver.ubuntu.com:80
>> * --recv-keys 2895100917357435
>>
>> Executing: /tmp/tmp.JwPNeUkm6x/gpg.1.sh --keyserver
>>
>> hkp://keyserver.ubuntu.com:80
>>
>> --recv-keys
>>
>> 2895100917357435
>>
>> gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
>>
>> gpg: key 17357435: public key "TLP Reaper packages <
>> rea...@thelastpickle.com>" imported
>>
>> gpg: Total number processed: 1
>>
>> gpg:   imported: 1  (RSA: 1)
>>
>>
>>
>>
>>
>> 2) Running apt-get update fails with:
>>
>>
>>
>> XXX:~$ sudo apt-get update
>>
>> Ign:1 https://dl.bintray.com/thelastpickle/reaper-deb wheezy InRelease
>>
>> Ign:2 https://dl.bintray.com/thelastpickle/reaper-deb wheezy Release
>>
>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>> Packages
>>
>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>> Packages
>>
>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
>> Packages
>>
>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en_US
>>
>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en
>>
>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>> Packages
>>
>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>> Packages
>>
>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
>> Packages
>>
>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en_US
>>
>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en
>>
>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>> Packages
>>
>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>> Packages
>>
>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
>> Packages
>>
>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en_US
>>
>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en
>>
>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>> Packages
>>
>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>> Packages
>>
>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
>> Packages
>>
>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en_US
>>
>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en
>>
>> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>> Packages
>>
>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>> Packages
>>
>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
>> Packages
>>
>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en_US
>>
>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en
>>
>> Err:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
>> Packages
>>
>>   Received HTTP code 403 from proxy after CONNECT
>>
>> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
>> Packages
>>
>> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
>> Packages
>>
>> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en_US
>>
>> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
>> Translation-en
>>
>> Ign:8 http://lnz-apt-cacher.dynatrace.vmta/apt xenial InRelease
>>
>> Hit:9

Re: Reaper 1.2 released

2018-07-25 Thread Abdul Patel 
I am trying to uograde to 1.2.2 version of reaper the instance isnt
starting and giving error that unable to create table snapshot ..do we need
to create it under reaper-db?

On Wednesday, July 25, 2018, Steinmaurer, Thomas <
thomas.steinmau...@dynatrace.com> wrote:

> Jon,
>
>
>
> eager trying it out.  Just FYI. Followed the installation instructions
> on http://cassandra-reaper.io/docs/download/install/ Debian-based.
>
>
>
> 1) Importing the key results in:
>
>
>
> XXX:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys
> 2895100917357435
>
> Executing: /tmp/tmp.tP0KAKG6iT/gpg.1.sh --keyserver
>
> keyserver.ubuntu.com
>
> --recv-keys
>
> 2895100917357435
>
> gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
>
> ?: [fd 4]: read error: Connection reset by peer
>
> gpgkeys: HTTP fetch error 7: couldn't connect: eof
>
> gpg: no valid OpenPGP data found.
>
> gpg: Total number processed: 0
>
> gpg: keyserver communications error: keyserver unreachable
>
> gpg: keyserver communications error: public key not found
>
> gpg: keyserver receive failed: public key not found
>
>
>
> I had to change the keyserver URL then the import worked:
>
>
>
> XXX:~$ sudo apt-key adv --keyserver *hkp://keyserver.ubuntu.com:80
> * --recv-keys 2895100917357435
>
> Executing: /tmp/tmp.JwPNeUkm6x/gpg.1.sh --keyserver
>
> hkp://keyserver.ubuntu.com:80
>
> --recv-keys
>
> 2895100917357435
>
> gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
>
> gpg: key 17357435: public key "TLP Reaper packages <
> rea...@thelastpickle.com>" imported
>
> gpg: Total number processed: 1
>
> gpg:   imported: 1  (RSA: 1)
>
>
>
>
>
> 2) Running apt-get update fails with:
>
>
>
> XXX:~$ sudo apt-get update
>
> Ign:1 https://dl.bintray.com/thelastpickle/reaper-deb wheezy InRelease
>
> Ign:2 https://dl.bintray.com/thelastpickle/reaper-deb wheezy Release
>
> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> Packages
>
> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> Packages
>
> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> Packages
>
> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en_US
>
> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en
>
> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> Packages
>
> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> Packages
>
> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> Packages
>
> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en_US
>
> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en
>
> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> Packages
>
> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> Packages
>
> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> Packages
>
> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en_US
>
> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en
>
> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> Packages
>
> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> Packages
>
> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> Packages
>
> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en_US
>
> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en
>
> Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> Packages
>
> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> Packages
>
> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> Packages
>
> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en_US
>
> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en
>
> Err:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64
> Packages
>
>   Received HTTP code 403 from proxy after CONNECT
>
> Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386
> Packages
>
> Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all
> Packages
>
> Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en_US
>
> Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main
> Translation-en
>
> Ign:8 http://lnz-apt-cacher.dynatrace.vmta/apt xenial InRelease
>
> Hit:9 http://pl.archive.ubuntu.com/ubuntu xenial InRelease
>
> Hit:10 http://lnz-apt-cacher.dynatrace.vmta/apt xenial Release
>
> Hit:11 http://pl.archive.ubuntu.com/ubuntu xenial-backports InRelease
>
> Hit:13 http://pl.archive.ubuntu.com/ubuntu xenial-security InRelease
>
> Hit:14 http://pl.archive.ubuntu.com/ubuntu xenial-updates

Re: Infinite loop of single SSTable compactions

2018-07-25 Thread James Shaw 
nodetool compactionstats  --- see compacting which table
nodetool cfstats keyspace_name.table_name  --- check partition side,
tombstones

go the data file directories:  look the data file size, timestamp,  ---
compaction will write to new temp file with _tmplink...,

use sstablemetadata ...    look the largest or oldest one first

of course, other factors may be,  like disk space, etc
also what are compaction_throughput_mb_per_sec in cassandra.yaml

Hope it is helpful.

Thanks,

James




On Wed, Jul 25, 2018 at 4:18 AM, Martin Mačura  wrote:

> Hi,
> we have a table which is being compacted all the time, with no change in
> size:
>
> Compaction History:
> compacted_atbytes_inbytes_out   rows_merged
> 2018-07-25T05:26:48.101 57248063878 57248063878 {1:11655}
>
>   2018-07-25T01:09:47.346 57248063878 57248063878
> {1:11655}
>  2018-07-24T20:52:48.652
> 57248063878 57248063878 {1:11655}
>
> 2018-07-24T16:36:01.828 57248063878 57248063878 {1:11655}
>
>   2018-07-24T12:11:00.026 57248063878 57248063878
> {1:11655}
>  2018-07-24T07:28:04.686
> 57248063878 57248063878 {1:11655}
>
> 2018-07-24T02:47:15.290 57248063878 57248063878 {1:11655}
>
>   2018-07-23T22:06:17.410 57248137921 57248063878
> {1:11655}
>
> We tried setting unchecked_tombstone_compaction to false, had no effect.
>
> The data is a time series, there will be only a handful of cell
> tombstones present. The table has a TTL, but it'll be least a month
> before it takes effect.
>
> Table properties:
>AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.TimeWindowCompactionStrategy',
> 'compaction_window_size': '1', 'compaction_window_unit': 'DAYS',
> 'max_threshold': '32', 'min_threshold': '4',
> 'unchecked_tombstone_compaction': 'false'}
>AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
>AND crc_check_chance = 1.0
>AND dclocal_read_repair_chance = 0.0
>AND default_time_to_live = 63072000
>AND gc_grace_seconds = 10800
>AND max_index_interval = 2048
>AND memtable_flush_period_in_ms = 0
>AND min_index_interval = 128
>AND read_repair_chance = 0.0
>AND speculative_retry = 'NONE';
>
> Thanks for any help
>
>
> Martin
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>

test email

2018-07-25 Thread R1 J1

Re: Reading cardinality from Statistics.db failed

2018-07-25 Thread Vitali Dyachuk 
I'm using 3.0.15. I see that there is some fix for sstable metadata in
3.0.16 https://issues.apache.org/jira/browse/CASSANDRA-14217 - is that a
fix for "reading cardinalyti from statistics.db" ?


On Wed, Jul 25, 2018 at 1:02 PM Hannu Kröger  wrote:

> What version of Cassandra are you running? There is a bug in 3.10.0 and
> certain 3.0.x that occurs in certain conditions and corrupts that file.
>
> Hannu
>
> Vitali Dyachuk  kirjoitti 25.7.2018 kello 10.48:
>
> Hi,
> I have noticed in the cassandra system.log that there is some issue with
> sstable metadata, the messages says:
> WARN  [Thread-6] 2018-07-25 07:12:47,928 SSTableReader.java:249 - Reading
> cardinality from Statistics.db failed for
> /opt/data/disk5/data/keyspace/table/mc-big-Data.db
> Although there is no such file. The message has appeared after i've
> changed the compaction strategy from SizeTiered to Leveled.
> Currently i'm running nodetool scrub to rebuilt the sstable, and it takes
> a lot of time to scrub all sstables.
> Reading the code it is said that if this metada is broken, then estimating
> the keys will be done using index summary. How expensive it is ?
>
> https://github.com/apache/cassandra/blob/cassandra-3.0.15/src/java/org/apache/cassandra/io/sstable/format/SSTableReader.java#L245
>
> The main question is why has this happened?
>
> Thanks,
> Vitali Djatsuk.
>
>

Infinite loop of single SSTable compactions

2018-07-25 Thread Martin Mačura 
Hi,
we have a table which is being compacted all the time, with no change in size:

Compaction History:
compacted_atbytes_inbytes_out   rows_merged
2018-07-25T05:26:48.101 57248063878 57248063878 {1:11655}

  2018-07-25T01:09:47.346 57248063878 57248063878
{1:11655}
 2018-07-24T20:52:48.652
57248063878 57248063878 {1:11655}

2018-07-24T16:36:01.828 57248063878 57248063878 {1:11655}

  2018-07-24T12:11:00.026 57248063878 57248063878
{1:11655}
 2018-07-24T07:28:04.686
57248063878 57248063878 {1:11655}

2018-07-24T02:47:15.290 57248063878 57248063878 {1:11655}

  2018-07-23T22:06:17.410 57248137921 57248063878
{1:11655}

We tried setting unchecked_tombstone_compaction to false, had no effect.

The data is a time series, there will be only a handful of cell
tombstones present. The table has a TTL, but it'll be least a month
before it takes effect.

Table properties:
   AND compaction = {'class':
'org.apache.cassandra.db.compaction.TimeWindowCompactionStrategy',
'compaction_window_size': '1', 'compaction_window_unit': 'DAYS',
'max_threshold': '32', 'min_threshold': '4',
'unchecked_tombstone_compaction': 'false'}
   AND compression = {'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
   AND crc_check_chance = 1.0
   AND dclocal_read_repair_chance = 0.0
   AND default_time_to_live = 63072000
   AND gc_grace_seconds = 10800
   AND max_index_interval = 2048
   AND memtable_flush_period_in_ms = 0
   AND min_index_interval = 128
   AND read_repair_chance = 0.0
   AND speculative_retry = 'NONE';

Thanks for any help


Martin

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

Re: Reading cardinality from Statistics.db failed

2018-07-25 Thread Hannu Kröger 
What version of Cassandra are you running? There is a bug in 3.10.0 and certain 
3.0.x that occurs in certain conditions and corrupts that file. 

Hannu

> Vitali Dyachuk  kirjoitti 25.7.2018 kello 10.48:
> 
> Hi,
> I have noticed in the cassandra system.log that there is some issue with 
> sstable metadata, the messages says:
> WARN  [Thread-6] 2018-07-25 07:12:47,928 SSTableReader.java:249 - Reading 
> cardinality from Statistics.db failed for 
> /opt/data/disk5/data/keyspace/table/mc-big-Data.db
> Although there is no such file. The message has appeared after i've changed 
> the compaction strategy from SizeTiered to Leveled.
> Currently i'm running nodetool scrub to rebuilt the sstable, and it takes a 
> lot of time to scrub all sstables.
> Reading the code it is said that if this metada is broken, then estimating 
> the keys will be done using index summary. How expensive it is ?
> https://github.com/apache/cassandra/blob/cassandra-3.0.15/src/java/org/apache/cassandra/io/sstable/format/SSTableReader.java#L245
> 
> The main question is why has this happened?
> 
> Thanks,
> Vitali Djatsuk.

RE: Reaper 1.2 released

2018-07-25 Thread Steinmaurer, Thomas 
Jon,

eager trying it out.  Just FYI. Followed the installation instructions on 
http://cassandra-reaper.io/docs/download/install/ Debian-based.

1) Importing the key results in:

XXX:~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 
2895100917357435
Executing: /tmp/tmp.tP0KAKG6iT/gpg.1.sh --keyserver
keyserver.ubuntu.com
--recv-keys
2895100917357435
gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
?: [fd 4]: read error: Connection reset by peer
gpgkeys: HTTP fetch error 7: couldn't connect: eof
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: keyserver unreachable
gpg: keyserver communications error: public key not found
gpg: keyserver receive failed: public key not found

I had to change the keyserver URL then the import worked:

XXX:~$ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 
2895100917357435
Executing: /tmp/tmp.JwPNeUkm6x/gpg.1.sh --keyserver
hkp://keyserver.ubuntu.com:80
--recv-keys
2895100917357435
gpg: requesting key 17357435 from hkp server keyserver.ubuntu.com
gpg: key 17357435: public key "TLP Reaper packages " 
imported
gpg: Total number processed: 1
gpg:   imported: 1  (RSA: 1)


2) Running apt-get update fails with:

XXX:~$ sudo apt-get update
Ign:1 https://dl.bintray.com/thelastpickle/reaper-deb wheezy InRelease
Ign:2 https://dl.bintray.com/thelastpickle/reaper-deb wheezy Release
Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64 Packages
Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386 Packages
Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all Packages
Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main 
Translation-en_US
Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main Translation-en
Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64 Packages
Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386 Packages
Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all Packages
Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main 
Translation-en_US
Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main Translation-en
Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64 Packages
Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386 Packages
Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all Packages
Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main 
Translation-en_US
Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main Translation-en
Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64 Packages
Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386 Packages
Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all Packages
Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main 
Translation-en_US
Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main Translation-en
Ign:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64 Packages
Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386 Packages
Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all Packages
Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main 
Translation-en_US
Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main Translation-en
Err:3 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main amd64 Packages
  Received HTTP code 403 from proxy after CONNECT
Ign:4 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main i386 Packages
Ign:5 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main all Packages
Ign:6 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main 
Translation-en_US
Ign:7 https://dl.bintray.com/thelastpickle/reaper-deb wheezy/main Translation-en
Ign:8 http://lnz-apt-cacher.dynatrace.vmta/apt xenial InRelease
Hit:9 http://pl.archive.ubuntu.com/ubuntu xenial InRelease
Hit:10 http://lnz-apt-cacher.dynatrace.vmta/apt xenial Release
Hit:11 http://pl.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:13 http://pl.archive.ubuntu.com/ubuntu xenial-security InRelease
Hit:14 http://pl.archive.ubuntu.com/ubuntu xenial-updates InRelease
Reading package lists... Done
W: The repository 'https://dl.bintray.com/thelastpickle/reaper-deb wheezy 
Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
E: Failed to fetch 
https://dl.bintray.com/thelastpickle/reaper-deb/dists/wheezy/main/binary-amd64/Packages
  Received HTTP code 403 from proxy after CONNECT
E: Some index files failed to download. They have been ignored, or old ones 
used instead.


Thanks,
Thomas

From: Jonathan Haddad 
Sent: Dienstag, 24. Juli 2018 21:08
To: user

Reading cardinality from Statistics.db failed

2018-07-25 Thread Vitali Dyachuk 
Hi,
I have noticed in the cassandra system.log that there is some issue with
sstable metadata, the messages says:
WARN  [Thread-6] 2018-07-25 07:12:47,928 SSTableReader.java:249 - Reading
cardinality from Statistics.db failed for
/opt/data/disk5/data/keyspace/table/mc-big-Data.db
Although there is no such file. The message has appeared after i've changed
the compaction strategy from SizeTiered to Leveled.
Currently i'm running nodetool scrub to rebuilt the sstable, and it takes a
lot of time to scrub all sstables.
Reading the code it is said that if this metada is broken, then estimating
the keys will be done using index summary. How expensive it is ?
https://github.com/apache/cassandra/blob/cassandra-3.0.15/src/java/org/apache/cassandra/io/sstable/format/SSTableReader.java#L245

The main question is why has this happened?

Thanks,
Vitali Djatsuk.