Name: riak
Owner: Deis
Description: Riak database for Deis v2
Created: 2015-10-20 19:57:56.0
Updated: 2018-03-01 17:52:58.0
Pushed: 2018-02-27 20:16:23.0
Homepage: http://deis.io
Size: 58
Language: Go
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
|
| Deis Workflow is no longer maintained.
Please read the announcement for more detail. |
|—:|—|
| 09/07/2017 | Deis Workflow v2.18 final release before entering maintenance mode |
| 03/01/2018 | End of Workflow maintenance: critical patches no longer merged |
| | Hephy is a fork of Workflow that is actively developed and accepts code contributions. |
This is a project for running Riak in a kubernetes cluster.
If you want to experiment with running this component in kubernetes, try this:
ke # builds and pushes the image
ke deploy
At this point, 3 nodes should come up. However, Riak provides a multi-phased approach to cluster administration that enables you to stage and review cluster-level changes prior to committing them. Our cluster is in a “staged” state which means that the cluster nodes are ready to speak with each other, but the transaction hasn't yet been completed. To commit these changes so the cluster will start replicating data, run
bectl --namespace=deis exec deis-riak-bootstrap riak-admin cluster plan
bectl --namespace=deis exec deis-riak-bootstrap riak-admin cluster commit
To see what's going on in your Riak cluster, feel free to poke and prod it by running
bectl --namespace=deis exec deis-riak-bootstrap riak-admin member-status
============================= Membership ==================================
us Ring Pending Node
---------------------------------------------------------------------------
d 32.8% -- 'riak@10.246.1.34'
d 32.8% -- 'riak@10.246.1.35'
d 34.4% -- 'riak@10.246.1.36'
---------------------------------------------------------------------------
d:3 / Leaving:0 / Exiting:0 / Joining:0 / Down:0
Follow the riak-admin documentation for more info on managing your cluster.
You should have 3 replicas of riak available after deploying initially. To scale up, you can do so with
bectl --namespace=deis scale rc deis-riak --replicas=10
Wait for all the replicas to come up, then
bectl --namespace=deis exec $DEIS_RIAK_POD_NAME riak-admin cluster plan
Review the changes are fit to your desire, then
bectl --namespace=deis exec $DEIS_RIAK_POD_NAME riak-admin cluster commit
To commit those changes.
All files that are to be packaged into the container should be written
to the rootfs/ folder.
Along with unit tests, Deis values functional and integration testing.
These tests should go in the _tests folder.