ring_creation_size with `riak-admin status`
mde at fleegix.org
Thu Jul 24 02:09:48 EDT 2014
Sorry to take some time to get back to this -- I have been travelling for
the past few days. I wish I could blame the Debian installer for my
problem. It doesn't actually fire up the service on installation.
In this case it was simply my lack of familiarity with the config syntax. I
saw the double-percent on all the comment lines, assumed that meant
'comment,' and didn't realize that a single percent would comment the line
out as well. The ring_creation_size relies on a built-in default, and so
that line is initially commented out.
Thanks for the assistance with this. :)
On Mon, Jul 21, 2014 at 11:19 PM, Sean Cribbs <sean at basho.com> wrote:
> At least one or more of your nodes must have started before you changed
> that setting. Debian pretty often will start a service immediately after
> its package is installed, which can be annoying. Assuming you didn't put
> any data in it yet, the solution is to take all of the nodes down, remove
> all files from /var/lib/riak/ring on all nodes, and then restart and rejoin
> the cluster.
> On Mon, Jul 21, 2014 at 8:48 AM, Matthew Eernisse <mde at fleegix.org> wrote:
>> Riak folks,
>> Hi, I'm new to Riak, and confused by something I've seen after setting up
>> a cluster. (Currently a 4-machine test cluster in EC2.)
>> After installing Riak on Ubuntu via the riak_1.4.9-1_amd64.deb, I very
>> meticulously set ring_creation_size to 256 in each app.config before
>> starting the service and adding it to the cluster.
>> But when I do `riak-admin status`, it displays a ring_creation_size value
>> of 64. Any idea what's going on here?
>> Thanks in advance for the help.
>> riak-users mailing list
>> riak-users at lists.basho.com
> Sean Cribbs <sean at basho.com>
> Software Engineer
> Basho Technologies, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users