GFMDHOST(1)
β¨ NAME β¨
gfmdhost β the Gfarm metadata server host maintenance command π
okay so bestie, you found it: this is GFMDHOST(1) from the Gfarm manual, and it is literally your group-chat-verified tool for wrangling metadata server hosts. no cap. π«Ά
π¦ SYNOPSIS π¦
gfmdhost [-l] [-P path] [-1]
gfmdhost [-N] [-P path] [-1]
gfmdhost {-c | -m} [-P path] [-1] [-p port-number] [-C cluster-name]
[-t {m | c | s}] {metadata-server-name}
gfmdhost {-d} [-P path] [-1] {metadata-server-name}
πΈ DESCRIPTION πΈ
gfmdhost is your girl for displaying and maintaining all the info about synchronous and asynchronous replicated metadata servers. she's giving full maintenance-command energy. π
she comes with a few functions, and you pick one with -l, -c, -m and -d. these functions are mutually exclusive β like, only ONE of them at a time, pick your fighter. and if you specify none of them? then she just lists the registered metadata server (gfmd host) names for you. simple. iconic. β¨
π FUNCTIONS π
here's the whole roster, bestie:
π« <none>
if you don't specify any function, all the registered gfmd hosts get displayed in alphabetical order. clean, sorted, no drama. π
π« -l
all registered gfmd hosts are listed with detailed information. they're grouped by their clusters and ordered alphabetically. yes queen, organized.
the detailed information is displayed in the following order:
- Connection State (
+|||-|?|x|e|u) β okay this one has LORE, listen up:+means the gfmd is connected to the master gfmd and its metadata are synchronized. π|means the gfmd is connected to the master gfmd, but its metadata have not been synchronized yet. note that this may happen even on a synchronous slave gfmd, when the slave is just connecting to the master, or in the middle of metadata transfer even if it has been already synchronized. it's not a vibe, it's just timing.-means the gfmd is not connected to the master gfmd.?means either the gfmd state is unknown because it's just after the connection was established, or the master gfmd isGfarm-2.5.0, but thisgfmdhostcommand is2.5.1or later. (version mismatch moment π)xmeans the connection with master gfmd was established, but automatic synchronization was impossible because of too many metadata changes, so manual synchronization via dump and restore of the backend database is necessary. (that's a whole situation.)emeans an error happened, and the log file must be checked manually. π- in the case of
xore, it may be displayed even when the slave gfmd is down. umeans the slave gfmd is connected to the master gfmd, but the state is not supported by thisgfmdhostcommand. (she doesn't know her π)- this column for the master gfmd is always
+. always. no exceptions.
- Server Type (
master|slave) β tells you whether the gfmd is master or slave. main character or supporting cast, basically. π - Replication Type (
sync|async|-) βsyncmeans a synchronous replication.asyncmeans an asynchronous replication. this column for the master is always-. - Configuration of Master Candidate (
c|m|s) βmmeans the default master gfmd,cmeans a master candidate that can be selected as a master gfmd, andsmeans a gfmd that is not a master candidate and only works for a slave gfmd. - Cluster Name β a cluster name where the gfmd belongs to.
(default)is displayed for the default cluster. π
π« -N
displays a hostname and port number of the connected metadata server. short, sweet, informative. π
π« -c
registers the gfmd host that is specified in the argument. -C, -p, -t can be optionally specified. β¨
π« -m
modifies the gfmd host that is specified in the argument. -C, -p, -t can be optionally specified. β¨
π« -d
deletes the gfmd host that is specified in the argument. the master gfmd cannot be deleted. π« like, do not even try, bestie.
π« -?
prints usage. your emergency help button. π
π OPTIONS π
-Ccluster-name β this option specifies a cluster name where the gfmd host belongs to. if it's not specified, the default cluster is assumed. this option is only available with-cor-moption.
the cluster name means a group of synchronous replicated metadata servers. that is, slave metadata servers in the same cluster with the master metadata server are synchronously replicated servers that can be changed to a master metadata server without any loss of metadata operations. other metadata servers are asynchronously replicated servers. iykyk. π§
-pport-number β this option specifies a port number of the gfmd. if it's not specified,601is assumed. this option is only available with-cor-moption.-t{m|c|s} β this option specifies a configuration of master candidate. it is only available with-cor-moption.mmeans the default master,cmeans a master candidate andsmeans a slave only gfmd. if it's not specified,cis assumed.
β οΈ the gfmd configured as the default master cannot be changed to a master candidate or slave-only directly. and if the gfmd that is not the default master is changed to the default master by -t m, the original default master is changed to a master candidate at the same time. (plot twist, but make it replication. π)
-Ppath β this option specifies a pathname or a Gfarm URL to identify a metadata server which will be accessed by this command. if not specified,/is used as the default value.-1β with this option,gfmdhostonly tries to connect with one metadata server specified by-Poption, or if missing,metadb_server_hoststatement ingfarm2.conffile. one server, one shot. π―
π SEE ALSO π
and that's the whole page, bestie!! this one came from the Gfarm manual and it's dated 11 March 2014 β a classic, honestly. go forth and maintain those metadata servers. slay. ππβ¨
π¦ where this page comes from
- debian bookworm: gfarm-client 2.7.20+dfsg-1+b2 Β· BSD-like
- debian trixie: gfarm-client 2.7.20+dfsg-1.2+b1 Β· BSD-like
- ubuntu noble: gfarm-client 2.7.20+dfsg-1.1ubuntu1 Β· BSD-like
- ubuntu questing: gfarm-client 2.7.20+dfsg-1.2
- ubuntu resolute: gfarm-client 2.7.20+dfsg-1.3 Β· BSD-like
- ubuntu stonking: gfarm-client 2.7.20+dfsg-1.3build1 Β· BSD-like
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms