Join the Community
and take part in the story

Configure a rawx service

  • Replace UID with an unused ID in your puppet file (use an incremental integer for exemple)
  • Replace port in the rawx block and in the rdir block with unused ones on your server

This is a horrible work on adding hard drives.


I can’t see newly added rawx after puppet apply.


Can someone explain why openio --oio-ns=OPENIO cluster unlockall is required to exec and when ?


Hello @yongsheng

If you run openio cluster list --oio-ns OPENIO, you will see the list of scored services on your cluster, aswell as their score. The score is an internal metric used to determine the health of a particular service in order to decide whether it should be chosen to accept a request.

Now, these scores can be locked to any value between 0-100, either because the service is newly registered (locked to 0), it was locked by an administrator, or in some other specific circumstances.

Thus the command openio --oio-ns=OPENIO cluster unlockall will release the scores on all the services on your cluster, so that they can evolve “naturally” according to your machine’s resources and load and guide the decision making capabilities of the internal load balancers.

Simply, when you see a locked service in “cluster list” while you want it to actually accept requests you should unlock it. (either by unlockall or specifically targeting it using openio cluster unlock --oio-ns OPENIO [service_type] [service_ip]:[service_port].