Releases: grobian/carbon-c-relay
Releases · grobian/carbon-c-relay
v3.1
3.1 (29-04-2017)
Note: this release is now autoconf-based, you should download the tar.gz file from the files below instead of relying on github's tar for the release tag if you don't want dependencies on autoconf, automake, bison and flex for the build.
New Features
- router a new
route using
clause was added tomatch
rules to
set the string to be used as key for consistent-hash based clusters.
Pull Request #235 - consistent-hash node traversal is now done through a binary search
instead of forward pointer chasing.
Bugfixes
- Issue #261
unable to use numeric instance name - Issue #262
DNS round-robin on any_of cluster doesn't rotate and causes lots of
hung connections - Issue #263
parser fails on%
in regular expressions, and exits with a crash - Issue #264
carbon_ch hash algorithm change between 2.6 and 3.0
v3.0
3.0 (2017-04-07)
Notes
- Parsing of the configuration file has changed implementation in this
version. Should you find problems with configurations that worked
fine before, please report the problem. - The use of
send statistics to
is now deprecated, use the new
statistics send to
instead. - The use of statistics controlling flags
-S
sending interval and-m
summary mode, are now deprecated because they can be set in the
configuration.
New Features
- collector statistics now can be controlled via the configuration
file using the newstatistics
clause. This overrides some command
line flags, and adds some new posibilities. - router the rewrite rule got a new replacement mode:
\.
This
mode replaces all dots with underscores in the matched group. A
combination with upper/lowercasing is possible, e.g.\_.
. - collector one can now set the internal statistics prefix
Issue #25
Issue #113
Issue #249.
Bugfixes
- Issue #249
send statistics
changes metric prefix from dots into underscores
v2.6
2.6 (2017-01-26)
New Features
- router
useall
is now also allowed forforward
andfailover
clusters - server hostnames are now re-resolved at every connect
Issue #115 - server when connecting to a hostname, now /all/ resolved addresses
are tried in order before failing - relay A new
-O
flag allows to set the minimum rules threshold
before trying to optimise the rules.
Bugfixes
- Issue #246
usingstop
in amatch
tule does not stop metrics from being
processed afterwards - Issue #206
some metrics are randomly prefixed with garbage characters
v2.5
Bugfixes
- Issue #239
segfault when date format is incorrect - Issue #242
dispatcher/aggregations broken (relay seems too slow)
v2.4
New Features
- router
match
rules now support avalidate
clause to do data
filtering, Issue #228,
Issue #142,
Issue #121,
Pull #127,
Pull #87.
Bugfixes
- server connection errors are no longer endlessly repeated
- Issue #240
'include' directive doesn't care about rewrites. - Issue #241
XXX characters being prepended to metrics when sent via UDP - Issue #204
relay is sending data randomly while kill -HUP happens
v2.3
Bugfixes
- Issue #213
Change to aggregates to not cause HUP to reload when more than 10
aggregates are defined. - Issue #214
-U
option doesn't set UDP receive buffer size. - Issue #218
zeros inserted after some metrics. - Issue #219
should fail if port is unavailable - Issue #224
segfault during SIGHUP
v2.2
New Features
- relay socket receive and send buffer sizes can be adjusted
the-U
option was introduced to allow setting the socket
buffer size in bytes, Issue #207.
Enhancements
- relay the listen backlog default got increased from 3 to 32
- server TCP_NODELAY is now set to improve small writes
Bugfixes
- Issue #188
SIGHUP leads to SIGSEGV when config didn't change, or a SIGHUP is
received while a previous HUP is being processed - Issue #193
race condition in aggregator leads to crash - Issue #195
assertion fails when reloading config - Issue #200
use after free during shutdown in aggregator - Issue #203
change default connection listen backlog - Issue #208
TCP_NODELAY should be off for connections relaying data - Issue #199
Various race conditions reported by TSAN
v2.1
Enhancements
- router the optimiser now tries harder to form groups of
consecutive rules that have a matching common pattern
Bugfixes
- Issue #180
include directive possibly overrides previous included components - Issue #184
router optimise doesn't work correctly with regex groups