Glusterfs Min-free-disk option Function Description

In scenarios where glusterfs's distributed volume (distriick) or distri composite volume is used, many people will be concerned about whether to fill up some brick, and other brick is relatively empty. What will happen?

Glusterfs provides a min-free-disk option that allows you to configure a threshold value for the remaining free space.

When the remaining space of a brick is less than min-free-disk, if the new file falls on this brick, a link (self-contained glusterfs, the actual file location is recorded on the extended attributes.) The file points to the brick where the actual file is located, and the actual file content points to the brick.

In this way, when the file is lookup, it will go to the hash location to lookup to a link file. Then, find the location of the actual file based on the corresponding xattr, and perform subsequent operations at the actual file location.

Min-free-disk can be configured through the command line. The Configuration value can be either a percentage or an absolute value. For example:

# gluster volume set volname min-free-disk 10%

Or

# gluster volume set volname min-free-disk 10GB

Of course, as mentioned above, this option only works for the new file, and the old file will still be written in the original position. If too many original files are written, the brick space will be fully occupied.

In addition, if all the brick data reaches the threshold, the original brick data is still written to the original brick, and the Brick may be full.

This article is from the "einstcrazy" blog, please be sure to keep this source http://einst.blog.51cto.com/9493625/1566373

Glusterfs Min-free-disk option Function Description