Agent Configuration
Concepts
The agent uses ini configuration files.
Considering a configuration like:
[env]
bar = 1
bar@n2 = 2
envis a sectionbaris a optionenv.baris a keyword.env.bar=1is a keyword operation.1is theenv.barkeyword value.@n2is a node scope for the keywordenv.bar
Policies
-
If a keyword appears in both
node.confandcluster.conf, the value from node.conf takes precedence. -
Sections only accept recognized keywords, with the exception of the
[env]and[labels]sections, which are open. -
More specific scoped values override less specific ones.
With the above section in a
svc1object configuration:# on n1: $ om svc1 config eval --kw env.bar 1 # on n2: $ om svc1 config eval --kw env.bar 2
Syntax validation
A syntax check is performed before finalizing any modifications made with either the set or edit commands.
om cluster config edit
om cluster config set --kw hb#test.type=unsupported
A direct modification to the configuration file is not validated and may disrupt the cluster. In such cases, you can perform a post-hoc validation using:
# verify the syntax of cluster.conf
om cluster config validate
# verify the syntax of node.conf
om node config validate
# verify the syntax of a svc configuration
om svc1 config validate