Cluster ready status for Riak S2
13vitamins at gmail.com
Fri Apr 1 09:13:26 EDT 2016
Actually, 'riak-admin wait-for-service <service> <nodename>' can be a good
way of checking if a Riak service has fully started. For example, 'riak-admin
wait-for-service riak_kv riak at 127.0.0.1' (
more details in http://littleriakbook.com/). This command will exit when
the service is finally up. A list of available services can be printed using
'riak-admin services'. I believe it should work with Riak S2 as well as
On Fri, Apr 1, 2016 at 3:30 PM, Jhonny Everson <khronnuz at gmail.com> wrote:
> Thank you Mark,
> I end up adding some markers on image initialization and I watch the
> docker container logs for this message before trying to use the instance.
> I tried using riak-cs ping, but unfortunately the ping was not enough.
> e.g. sometimes the riak kv was still initialising when I got a ping
> response from riak-cs.
> On Fri, Apr 1, 2016 at 12:53 AM, Mark Allen <mrallen1 at yahoo.com> wrote:
>> You could try a `riak-cs ping` command and make sure it gets a "pong"
>> response as output. That's not a solid guarantee that everything's totally
>> started, but its better than just sleeping and hoping for the best.
> Jhonny Everson
> riak-users mailing list
> riak-users at lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users