You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 1, 2020. It is now read-only.
So starting riak cluster as per documention
`DOCKER_RIAK_AUTOMATIC_CLUSTERING=1 DOCKER_RIAK_CLUSTER_SIZE=5 DOCKER_RIAK_BACKEND=leveldb make start-cluster``
After stabilization I'll check for ring ownership; "ring_ownership": "[{'[email protected]',64}]",
Thats uncool.
So docker-enter into one of the nodes to see what riak-admin cluster plan shows
@kakoni, I had similar issues with unfinished cluster configuration. After digging into it I figured out that sometimes automatic_clustering.sh is executed too soon and 'cluster join' command returns "Node not found!" message. I wasn't able to come up with a quick fix for this issue and chose an alternative option: instead of joining the cluster from inside the container I'm doing it explicitly in start-cluster.sh, see bdb49dd and 83ff81f.
These changes give me consistently stable behaviour.
Hope this helps.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So starting riak cluster as per documention
`DOCKER_RIAK_AUTOMATIC_CLUSTERING=1 DOCKER_RIAK_CLUSTER_SIZE=5 DOCKER_RIAK_BACKEND=leveldb make start-cluster``
After stabilization I'll check for ring ownership;
"ring_ownership": "[{'[email protected]',64}]",
Thats uncool.
So docker-enter into one of the nodes to see what riak-admin cluster plan shows
Outstading changes, I'll commit them and check the status again
All good. And obviously ring ownership also cool now
"ring_ownership": "[{'[email protected]',13},\n {'[email protected]',13},\n {'[email protected]',13},\n {'[email protected]',13},\n {'[email protected]',12}]",
So something with automatic_clustering fails here.
The text was updated successfully, but these errors were encountered: