Rebuild a Volume: Meta2


First, run gridinit_cmd restart @meta2; this allows you to check if meta services are up. If scores are low, the rebuilder can take a long time and can fail due to a timeout. You can check the score by running openio cluster list meta2.

Launch rebuilding

You can launch the rebuild by using the openio-admin meta2 rebuild command:

# openio-admin meta2 rebuild
OPENIO|045256CF2FA8BBEAC689666EBA5BD7E9A7BFE76BA2E6511CC9C012B98125F56C OK None
OPENIO|DFB66CDA3F33A74B4A9E69B09D06159A36DA81EA9AD7C2BF8C899D352CE4E1E7 OK None
OPENIO|DD506C822AA5E2FC32C274C28FCC801F14B9CF5FA46602ED811B1C972F399BD3 OK None


If you want more information about current rebuilding, you can change the report interval using the --report-interval option. The default value is set to 3600 seconds, but if you want a report every minute, you can launch rebuilding using openio-admin meta2 rebuild --report-interval 60.

By default, rebuilding uses only one worker; you can set a number of workers using the --workers option. For example, openio-admin meta2 rebuild --workers 42 launches rebuilding using 42 workers.

Workers have a limited number of references to rebuild per seconds, 30 by default: the goal is to maintain the cluster performance during the rebuilding. You can change this value using the --items-per-second option. If you want to unlimit the number of references to rebuild per second, you can use openio-admin meta2 rebuild --items-per-second 0.