database-ttl verifiedimportantWritten by the Hub
How long settings are cached
in the configuration this is a line
database-ttl: 600Seconds between re-reads of the settings database; within that window the engine works entirely from memory and never queries the database per message.
Values
- Values
positive integer- Default
600 · taken from the build- applying
restart required- where it can be set
in the config file · with a startup flag · as an environment variable
In detail
MailerQ does not look anything up while sending. It loads every table into memory and repeats that every database-ttl seconds, which is what lets a node sustain high volume against a modest database — and what makes a direct SQL edit appear to do nothing. Lowering this value shortens the wait at the price of a full reload of every table on every cycle; raising it makes a cluster slower to accept changes. Neither is normally worth doing, because the exchange message described in mq5.concept.settings-propagation makes the change immediate regardless of this value.
What happens if you get it wrong
A row is written directly and no reload message is sent.The change is invisible for up to this many seconds, and looks like a lost write.verified by experiment · inference