Hi Daniel,
It should be safe, yes. If you run the `cluster leave` commands, then run
`cluster plan` (but don't yet run `cluster commit`), the output will show
if there's any violations in spreading each of your 3 copies around the
cluster. If it does provide a warning, you can `cluster clear` an
Hi Steven,
Based on that log output, it looks like you're running into issues with
system limits, probably open file limits. You can check the value that
Riak has available by connecting to one of the nodes with riak attach, then
executing:
```
os:cmd("ulimit -n").
```
(After, disconnect with c
Hi Alex,
The claimant node is used in operations related to adding/removing nodes
from the cluster, things like that. If the node dies, for example, due to
hardware failure, then the cluster will still continue to operate
normally. In this regard, there's nothing special about the claimant
node.
Hi Toby,
If you put another user into the config, that's all it takes to make them
the admin user. There's no special value that's set in the database
itself. Any user can be an admin user, it doesn't even have to be the
first one created. It's just whatever user you have set in the config.
Ki
Hi Toby,
> I thought that it was recommended AGAINST talking to a co-located Riak on
the same host?
I'm not sure where you heard that from, but that's not the case. We do
discourage running other parts of an application on the same hosts, such as
client front-ends for example. From the top of m
Hi Henning,
So normally, a bucket's custom properties are stored in the ring file.
It's this file which is gossiped around regularly in a cluster. When users
create hundreds/thousands of custom customer properties (it's been done),
it can grind the cluster almost to a standstill.
A bucket-type on
Hi Neo,
1) When building from source, the version numbers never show. They only
appear in the packaged versions. That's why you're not seeing them.
2) After creating the admin user - did you change anonymous_user_creation
back to 'off'?
3) I'm not entirely clear on what you did there - did you
