1.1.0 (02.07.2019)

Enhancements

(1033) Zookeeper multi datacenter

With the multi Zookeeper clusters, it's possible to increase Hermes isolation between data-centres.

In the end this change increase high-availability of Hermes.

Changes are only in hermes-management module which from now on can operate on multiple Zookeeper clusters.

To match Kafka clusters with Zookeeper clusters we have an additional field in a hermes-config called datacenter.

This field allows you to tell Hermes which Zookeeper cluster belongs to which Kafka cluster.

When there is only one Zookeeper cluster then it will be used for every Kafka cluster.

If you're migrating from previous version you need to add storage.clusters field in hermes-config and move storage.connectionString inside it (datacenter field is irrelevant when you have only 1 Zookeeper cluster).

Example:

kafka:
  clusters:
    -
      datacenter: dc1
      clusterName: kafka_primary
      connectionString: kafka-zookeeper:2181/clusters/dc1
    -
      datacenter: dc2
      clusterName: kafka_secondary
      connectionString: kafka-zookeeper:2181/clusters/dc2

storage:
  pathPrefix: /run/hermes
  clusters:
    - 
      datacenter: dc
      clusterName: zk
      connectionString: zookeeper:2181

1.0.7 (01.07.2019)

Bugfixes

(1053) Maximum possible offset to be committed for partition

1.0.6 (28.06.2019)

Enhancements

(1048) Exposed volume metric in metrics query endpoint

(1045) Enabled caching for dependencies on Travis

Bugfixes

(1050) Catch exceptions thrown while stopping kafka consumers

1.0.5 (25.06.2019)

Enhancements

(1042) Consumer group diagnostics tab in console

(1041) Added volume counter

Bugfixes

(1040) Clearing stale offsets, partition assignment term introduced

1.0.4 (17.06.2019)

Enhancements

(1035) Handling unparsable values in queries

Bugfixes

(1038) Fix to filtering duplicated signals

1.0.3 (10.06.2019)

Enhancements

(1032) Fixing MPSC queue's drain method to return all items

1.0.2 (06.06.2019)

Enhancements

(1031) Added logging related to offsets committing

(1025) ReadOnly mode for Management

This feature allows to manually switch Hermes Management to ReadOnly mode.
During maintenance mode this protects Hermes from any unexpected changes.
Switch is done at runtime via /mode admin endpoint.

Bugfixes

(1031) Fixed monitored MPSC queue utilization meter

1.0.1 (29.05.2019)

Enhancements

(1029) Attaching Keep-Alive header to frontend responses

Added option frontend.keep.alive.header.enabled (default false) to enable attaching Keep-Alive header with timeout
parameter (defined by frontend.keep.alive.header.timeout.seconds) to Hermes Frontend responses.

Bugfixes

(1027) Message sending handlers triggered only when consumer is running

(1028) Improved handling unavailable metrics

1.0.0 (16.05.2019)

After 5 years of developing and maintaining Hermes, we are very excited to announce that version 1.0
has been released. 🎊 🥳 🎂

Version 1.0 is symbolic. It doesn’t contain any changes in Hermes in comparison to the previous one.
It’s a cut-off from stable and mature code.

0.16.2 (24.04.2019)

Enhancements

(1019) Extended offline clients by 'owners' field