Hello Stefan.
Yes, initially I was working using docker without docker-compose, but for convenience and because I didn't know the restriction about compose, I decided to use compose at the end. I'll update my repository with the work that I have on bash.
2) Ability to scale (expand or shrink) the C* cluster via the orchestration method from 1) after the initial installation.1) Orchestration of C* cluster setup via bashHere are two things I am looking for:Hello Ruben,Thank you for your research. I see the repository contains docker-compose functionality. Unless something changed recently, docker-compose is no-go for orchestration.
Did you do any work or investigation regarding 1 and 2 above?
Thank you,
Stefan Negrea
On Wed, Sep 28, 2016 at 10:05 PM, Ruben Vargas Palma <rvargasp@redhat.com> wrote:
I was testing a little bit with Hawkular-Services + Cassandra cluster
using docker containers, I created a GitHub repository with my setup:
https://github.com/rubenvp8510/hwk-cassandra-docker
It seems to work fine, at least on my environment, I did some different
tests but I couldn't test more than 3 nodes on my machine, but hopefully
it will work for N nodes.
Some issues I found:
- Sometimes hawkular throws a timeout exception "Cassandra timeout
during read query at consistency LOCAL_ONE", I only managed to reproduce
it 2 times.
- This setup is not enough robust because the Keyspace has replica
factor of 1, so if one node dies hawkular-services started complain
about it.
Regards
_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
_______________________________________________ hawkular-dev mailing list hawkular-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev