mfschunkserver.cfg - main configuration file for mfschunkserver
The file mfschunkserver.cfg contains the configuration of the LizardFS chunkserver process.
OPTION = VALUE
Lines starting with the # character are ignored.
- where to store files with usage statistics and daemon lock file
- the label of this chunkserver (for tiering)
- user to run daemon as
- group to run daemon as (optional - if empty then default user group will be used)
- name of process to place in syslog messages (default is mfschunkserver)
- whether to perform mlockall() to avoid swapping out mfschunkserver process ( default is 0, i.e. no)
- nice level to run daemon with (default is -19 if possible; note: process must be started as root to increase priority)
- address of LizardFS master host to connect with (default is mfsmaster)
- number of LizardFS master port to connect with (default is 9420)
- delay in seconds before trying to reconnect to the master server after disconnection (default is 5)
- timeout (in seconds) for the master server connection (default is 60, minimum is 0.01)
- local address to use for connecting with the master server (default is *, i.e. default local address)
- IP address to listen on for client (mount) connections (* means any)
- port to listen on for client (mount) connections (default is 9422)
- timeout (in seconds) for client (mount) connections (default is 5)
- alternative name of mfshdd.cfg file
- free space threshold to set volume as 100% utilized when there is less than given amount of free space left (default is “4GiB”). This number is always added to the used disk space reported by chunkserver.
- chunk test period in seconds (default is 10)
- whether to remove each chunk from page when closing it to reduce cache pressure generated by chunkserver (default is 0, i.e. no)
- if enabled then chunkserver detects zero values in chunk data and frees corresponding file blocks (decreasing file system usage). This option works only on Linux and only with file systems supporting punching holes (XFS, ext4, Btrfs, tmpfs)
- limit how many kilobytes can be replicated from other chunkservers to this chunkserver in every second (by default undefined, i.e. no limits)
- number of threads which handle (in a round-robin manner) connections with clients (default is 1); these threads are responsible for reading from sockets and copying data from internal buffers to sockets
- number of threads that each network worker may use to do disk operations like opening chunks, reading or writing them (default is 2)
- additional number of kilobytes which should be passed to posix_fadvise(POSIX_FADV_WILLNEED) before reading data from a chunk (default is 0, i.e. use posix_fadvise only with the amount of data that is really needed; the value is aligned down to 64 KiB)
- try to fix out-of-order read requests; the value tells how much of skipped data to read if an offset of some read operation is greater than the offset where the previos operation finished (default is 0, i.e. don’t read any skipped data; the value is aligned down to 64 KiB)
- whether to create new chunks in the MooseFS format (signature + <checksum> + <data block>) or in the newer interleaved format ([<checksum> <data block>]*). (Default is 1, i.e. new chunks are created in MooseFS format)
- call fsync() after a chunk is modified (default is 1, i.e. enabled)
Copyright 2008-2009 Gemius SA, 2013-2016 Skytechnology Sp. z o.o.
LizardFS is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, version 3.
LizardFS is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with LizardFS. If not, see <http://www.gnu.org/licenses/>.