|author||Christian Grothoff <email@example.com>||2021-09-03 19:13:42 +0200|
|committer||Christian Grothoff <firstname.lastname@example.org>||2021-09-03 19:13:42 +0200|
document new s aggregator sharding
2 files changed, 7 insertions, 0 deletions
diff --git a/manpages/taler-exchange-aggregator.1.rst b/manpages/taler-exchange-aggregator.1.rst
index cf8f3ed..4a15c22 100644
@@ -27,6 +27,10 @@ Description
to the same merchant into larger wire transfers. The actual transfers are then
done by **taler-exchange-transfer**.
+The AGGREGATOR_SHARD_SIZE option can be used to allow multiple aggregator processes to run in parallel and share the load. This is only recommended if a single aggregator is insufficient for the workload.
+The aggregator uses a special table to lock shards it is working on. If an aggregator process dies (say due to a power failure), these shard locks may prevent the aggregator from resuming normally. In this case, you must run "taler-exchange-dbinit -s" to release the shard locks before restarting the aggregator.
**-c** *FILENAME* \| **--config=**\ \ *FILENAME*
Use the configuration and other resources for the exchange to operate
diff --git a/manpages/taler.conf.5.rst b/manpages/taler.conf.5.rst
index ee67358..0aa24e2 100644
@@ -119,6 +119,9 @@ AGGREGATOR_IDLE_SLEEP_INTERVAL
For how long should the aggregator sleep when it is idle
before trying to look for more work? Default is 60 seconds.
+ Which share of the range from [0,..2147483648] should be processed by one of the shards of the aggregator. Useful only for Taler exchanges with ultra high-performance needs. When changing this value, you must stop all aggregators and run "taler-exchange-dbinit -s" before resuming. Default is 2147483648 (no sharding).
For how long are signatures with signing keys legally valid?