Andrew Jefferson

This can skip many many more messages than the one that caused the error. This can arise when a call to commitOffset fails because of "rebalanceInProgress" What should I do...

retry with timeout doesn't seem very safe. I am pretty sure that there are various intermittent network scenarios where that could still result in skipping messages. Having an option to...

Apologies on my misuse of the terminology around LATEST_OFFSET - I would like the consumer to either fail catastrophically or fetch using the last committed offset if there is an...

It looks to me like the failover_timeout logic is not quite right in mesoslib.go see here: http://mesos.apache.org/documentation/latest/high-availability-framework-guide/ - recommended settings are much greater than the 60 seconds that is set...

See this PR which fixes the behaviour when a scheduler is restarted: https://github.com/mesos/mr-redis/pull/57

Hi @dhilipkumars We're running it by installing the package from universe then going into Marathon and changing the docker image to point at out docker image: https://hub.docker.com/r/tractableio/mr-redis/

We also had to change the docker client API version setting in mr-redis to match the version of Docker running on our Agents before we built that docker image. You...

I guess I could push a new version to the universe, but I wouldn't want to push something that includes code changes that aren't in this (mainline) repo. Furthermore for...

n.b. this is the commit I am concerned about: https://github.com/eastlondoner/mr-redis/commit/10bdba0c36e5f007fe8e0f9a5b9600ad46c4fb93

@daguero I don't work at Tractable anymore and I recall I did some hacky things that I didn't want to publish to make it work. However you should be able...