Add cautionary note re delay_reaping in account-server.conf-sample
Change-Id: I2c3eea783321338316eecf467d30ba0b3217256c Related-Bug: #1514528
This commit is contained in:
parent
ff23dcdf3a
commit
93fc9d2de8
@ -386,7 +386,11 @@ Connection timeout to external services. The default is 0.5 seconds.
|
|||||||
.IP \fBdelay_reaping\fR
|
.IP \fBdelay_reaping\fR
|
||||||
Normally, the reaper begins deleting account information for deleted accounts
|
Normally, the reaper begins deleting account information for deleted accounts
|
||||||
immediately; you can set this to delay its work however. The value is in
|
immediately; you can set this to delay its work however. The value is in
|
||||||
seconds. The default is 0.
|
seconds. The default is 0. The sum of this value and the
|
||||||
|
container-updater interval should be less than the account-replicator
|
||||||
|
reclaim_age. This ensures that once the account-reaper has deleted a
|
||||||
|
container there is sufficient time for the container-updater to report to the
|
||||||
|
account before the account DB is removed.
|
||||||
.IP \fBreap_warn_after\fR
|
.IP \fBreap_warn_after\fR
|
||||||
If the account fails to be be reaped due to a persistent error, the
|
If the account fails to be be reaped due to a persistent error, the
|
||||||
account reaper will log a message such as:
|
account reaper will log a message such as:
|
||||||
|
@ -1650,7 +1650,15 @@ delay_reaping 0 Normally, the reaper begins deleting
|
|||||||
account information for deleted accounts
|
account information for deleted accounts
|
||||||
immediately; you can set this to delay
|
immediately; you can set this to delay
|
||||||
its work however. The value is in seconds,
|
its work however. The value is in seconds,
|
||||||
2592000 = 30 days, for example.
|
2592000 = 30 days, for example. The sum of
|
||||||
|
this value and the container-updater
|
||||||
|
``interval`` should be less than the
|
||||||
|
account-replicator ``reclaim_age``. This
|
||||||
|
ensures that once the account-reaper has
|
||||||
|
deleted a container there is sufficient
|
||||||
|
time for the container-updater to report
|
||||||
|
to the account before the account DB is
|
||||||
|
removed.
|
||||||
reap_warn_after 2892000 If the account fails to be be reaped due
|
reap_warn_after 2892000 If the account fails to be be reaped due
|
||||||
to a persistent error, the account reaper
|
to a persistent error, the account reaper
|
||||||
will log a message such as:
|
will log a message such as:
|
||||||
|
@ -203,7 +203,11 @@ use = egg:swift#recon
|
|||||||
#
|
#
|
||||||
# Normally, the reaper begins deleting account information for deleted accounts
|
# Normally, the reaper begins deleting account information for deleted accounts
|
||||||
# immediately; you can set this to delay its work however. The value is in
|
# immediately; you can set this to delay its work however. The value is in
|
||||||
# seconds; 2592000 = 30 days for example.
|
# seconds; 2592000 = 30 days for example. The sum of this value and the
|
||||||
|
# container-updater interval should be less than the account-replicator
|
||||||
|
# reclaim_age. This ensures that once the account-reaper has deleted a
|
||||||
|
# container there is sufficient time for the container-updater to report to the
|
||||||
|
# account before the account DB is removed.
|
||||||
# delay_reaping = 0
|
# delay_reaping = 0
|
||||||
#
|
#
|
||||||
# If the account fails to be reaped due to a persistent error, the
|
# If the account fails to be reaped due to a persistent error, the
|
||||||
|
Loading…
Reference in New Issue
Block a user