mirror of
https://github.com/saltstack/salt.git
synced 2025-04-17 10:10:20 +00:00
Data cache plugin configuration documentation.
This commit is contained in:
parent
c7209cd90c
commit
dad748f57a
2 changed files with 22 additions and 4 deletions
|
@ -127,9 +127,13 @@
|
|||
# the jobs system and is not generally recommended.
|
||||
#job_cache: True
|
||||
|
||||
# Cache minion grains and pillar data in the cachedir.
|
||||
# Cache minion grains, pillar and mine data via the cache subsystem in the
|
||||
# cachedir or a database.
|
||||
#minion_data_cache: True
|
||||
|
||||
# Cache subsystem module to use for minion data cache.
|
||||
#cache: localfs
|
||||
|
||||
# Store all returns in the given returner.
|
||||
# Setting this option requires that any returner-specific configuration also
|
||||
# be set. See various returners in salt/returners for details on required
|
||||
|
|
|
@ -459,14 +459,28 @@ jobs dir.
|
|||
Default: ``True``
|
||||
|
||||
The minion data cache is a cache of information about the minions stored on the
|
||||
master, this information is primarily the pillar and grains data. The data is
|
||||
cached in the Master cachedir under the name of the minion and used to
|
||||
predetermine what minions are expected to reply from executions.
|
||||
master, this information is primarily the pillar, grains and mine data. The data
|
||||
is cached via the cache subsystem in the Master cachedir under the name of the
|
||||
minion or in a supported database. The data is used to predetermine what minions
|
||||
are expected to reply from executions.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
minion_data_cache: True
|
||||
|
||||
.. conf_master:: cache
|
||||
|
||||
``cache``
|
||||
---------------------
|
||||
|
||||
Default: ``localfs``
|
||||
|
||||
Cache subsystem module to use for minion data cache.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
cache: consul
|
||||
|
||||
.. conf_master:: ext_job_cache
|
||||
|
||||
``ext_job_cache``
|
||||
|
|
Loading…
Add table
Reference in a new issue