search

go-graphite / carbonzipper

proxy to transparently merge graphite carbon backends
Other
104 stars 29 forks source link

When will the stretch deb file for carbonzipper be available? #71

Open dreddynarahari opened 6 years ago

dreddynarahari commented 6 years ago

When will the latest version stretch deb file for carbonzipper be uploaded into https://packagecloud.io/go-graphite/stable ?

I presently see 0.72 version for trusty available at the above link.

Civil commented 6 years ago

Hm, I'll try to have a look on packaging during the weekends or so, as there should be packages for stretch. Though new versions are merged with carbonapi and next version will be built from there.

dreddynarahari commented 6 years ago

May I know what is the current stable version compatibility the below components to have a working system?

  1. graphite-web -> carbonzipper -> go-carbon -> carbon-c-relay?
  2. carbonapi -> carbonzipper -> go-carbon -> carbon-c-relay ?
gunnihinn commented 6 years ago

At Booking.com we're running:

We can vouch for this being a good combination. I'm not sure about our version of graphite-web, I'll check tomorrow.

dreddynarahari commented 6 years ago

Thank you. Will wait for your response on graphite-web version.

Civil commented 6 years ago

any version of graphite-web should be compatible with 0.73, though it was tested with 0.9.12 and 1.1.3 only.

  1. carbon-c-relay uses standard text protocol so any version should be compatible with any version of go-carbon. As about version at booking.com they are using 2.6 as it's the most stable one. Up to you if you want to try newer.
  2. carbonapi, zipper and go-carbon in theory should be compatible in terms of protocols, though the versions mentioned by @gunnihinn are the most stable ones. Newer versions of carbonapi have more features, but they were not stable/fast enough on large scale environments.
gunnihinn commented 6 years ago

As about version at booking.com they are using 2.6 as it's the most stable one. Up to you if you want to try newer.

We're on 2.6 mostly because we've seen data corruption at the scale we run things in the newer versions. Some of the problems we see are related to backwards-compatibility with decisions we made a long time ago. You may not run into those issues and the newer versions may be fine for you, but caveat emptor.

Newer versions of carbonapi have more features, but they were not stable/fast enough on large scale environments.

Again why we're running the older versions of carbonapi/carbonzipper. We're putting a lot of effort into making the current versions stable and fast enough to run at our scale, but we're not there yet. They seem stable enough by now, but the performance isn't up to par with the older versions. And again, this may not be a problem for you. If you want to try the latest version of carbonapi, you probably won't need to run a separate carbonzipper instance, as carbonapi has taken over its functionality.

dreddynarahari commented 6 years ago

Thank you for the info. @Civil Can you let me know when will carbonzipper debian packages for stretch will be made available on https://packagecloud.io/go-graphite/stable ?