mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dhilip Kumar S <dhilip.kuma...@huawei.com>
Subject A Redis Framework for Apache Mesos
Date Fri, 01 Jul 2016 23:03:20 GMT
Hello All,

We have built a framework for provisioning redis-servers in Apache Mesos enabled infrastructure.
It would be awesome to get communities feedback. While mesos ecosystem is strengthening its
capability in storage layer, redis could be an addition to the lineup.  This is primarily
intended for providers who would like to host redis as a service in their infrastructure.

There is an elaborate README about the project which should help in setting it up: https://github.com/mesos/mr-redis.
Please let us know if there is anything missing in the documentation by raising a PR or opening
an issue or even writing to us.

This project is also packaged as  mr-redis with DCOS so should be pretty straight forward
to install it via DCOS CLI or DCOS GUI.

(A Step by Step guide is provided in the README for your convenience)

Salient Features of this project include:

1)      Create multiple redis clusters (Master-Slave Cluster) with ease

2)      Redis instances recover in seconds and not in minutes

3)      If a Master fails a slaves is automatically promoted as the New master, all the old
slaves now replicate from the newly master plus a new slave is added to the cluster.  All
this without using redis-sentinel in your datacenter and all these happens in a couple of
seconds.

4)      A CLI to perform basic operations such as create / status / delete redis instances
on the fly.  CLI is cross compiled for Windows and Darwin users too.

5)      Scheduler is a HTTP REST server which also can respond to simple Angular UI we have
built to get started with.  Instructions on how to setup the UI is here. https://github.com/mesos/mr-redis/tree/master/ui/app

We also had an opportunity to talk about this during the recent MesosCon 2016: https://www.youtube.com/watch?v=xe-Gom5tOl0&index=32&list=PLGeM09tlguZQVL7ZsfNMffX9h1rGNVqnC

Future Work:

*         Implement a proxy technique to expose one single endpoint for the redis instance.

*         Implement Memory Cgroups per redis PROCS

*         Add support for Redis 3.0 cluster instances (Adding shards to a running redis instance)

*         Implement integration test suite and benchmarking suite to the framework.

Special thanks to Adobe.io team who expressed interest in collaborating in the development
of this product. I'm sure it's going to be great working with all of you folks.

Advanced happy Independence day America and happy weekend rest of the world.

Looking forward to hear from you all,
Dhilip

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message