git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reaper 1.2 released


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.steinmaurer@xxxxxxxxxxxxx> 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 <reaper@xxxxxxxxxxxxxxxxx>" 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 <jon@xxxxxxxxxxxxx>
Sent: Dienstag, 24. Juli 2018 21:08
To: user <user@xxxxxxxxxxxxxxxxxxxx>
Subject: Reaper 1.2 released

 

Hey folks,

 

Just wanted to share with the list that after a bit of a long wait, we've released Reaper 1.2.  We have a short blog post here outlining the new features: https://twitter.com/TheLastPickle/status/1021830663605870592

 

With each release we've worked on performance improvements and stability as our primary focus.  We're helping quite a few teams manage repair on hundreds or thousands of nodes with Reaper so first and foremost we need it to work well at that sort of scale :) 

 

We also recognize the need for features other than repair, which is why we've added support for taking & listing cluster wide snapshots. 

 

Looking forward, we're planning on adding support for more operations and reporting - we're already got some code to pull thread pool stats and we'd like to expose a lot of table level information as well.  

 

http://cassandra-reaper.io/

 

Looking forward to hearing your feedback!

--

Jon Haddad
Principal Consultant, The Last Pickle

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a company registered in Linz whose registered office is at 4040 Linz, Austria, Freistädterstraße 313