Giulio Eulisse

DPL: handle Lifetime::Condition in consumeWhenAny

6

Conditions should never be consumed, unless there is data.

DPL: move responsibility to get services

22

Responsibility to access services is now moved to the newly introduced ServiceRegistryRef. This will cache the information about the current stream / thread (and in the future the multiplexed DataProcessor)...

Using this or Marathon?

1

Could you please highlight what would be the advantage of using this compared to (say) Marathon spawning elasticsearch instances on its own?

This PR includes the changes I've locally in my setup. In particular it provides the following improvements: - Adds support for CI on [Travis](https://travis-ci.org/). - Moves to more recent versions...

Hi, I'd like to run ElasticSearch nodes only on specific slaves which match the `elasticsearch:CLUSTER:data` attribute in mesos. Is there a way to do so?