Updated Erasure coding for warm storage (markdown)

Chris Lu 2019-06-10 15:00:19 -07:00
parent 2f81310581
commit 7fb8617100

@ -10,11 +10,13 @@ Run `weed scaffold -conf=master` to generate a `master.toml` file, put it in cur
It will add a list of commands executed periodically. Actually the commands can also be executed via `weed shell` with exactly the same effect. The scripts stored in the `master.toml` file is to make the deployment convenient. It will add a list of commands executed periodically. Actually the commands can also be executed via `weed shell` with exactly the same effect. The scripts stored in the `master.toml` file is to make the deployment convenient.
The script in the `master.toml` is executed on the master. If you have a large number of EC volumes, processing all of them on master may cost some CPU resources. It's better to run them with `weed shell` via some cron job in a separate machine.
## How the scripts works? ## How the scripts works?
The scripts have 3 steps related to erasure coding. The scripts have 3 steps related to erasure coding.
### Erasure Encode Sealed Data ### Erasure Encode Sealed Data
`ec.encode` command will find volumes that are almost full and has been stale for a period of time. `ec.encode` command will find volum`es that are almost full and has been stale for a period of time.
The default command is `ec.encode -fullPercent=95 -quietFor=1h`. It will find volumes at least 95% of the maximum volume size, which is usually 30GB, and has no updates for 1 hour. The default command is `ec.encode -fullPercent=95 -quietFor=1h`. It will find volumes at least 95% of the maximum volume size, which is usually 30GB, and has no updates for 1 hour.