Restarting kumo

get-help
1

Hello, i have some messages in the scheduled queues, and due to many messages being temporary defered by yahoo, i would like to change the max_message_rate = “10/s” for yahoo in the shaping file. If i do the changes and restart kumo, would the queues be emptied?

2

Hey there @yummy-echidna, thanks for posting. Please read the “Troubleshooting” and “How to Ask for Help” buttons below. If you would like a 1:1 support session from the KumoMTA team, details are at the “Book a Support Session” button below.

3

Configuration information is cached, so you don’t need to restart the server after changing your shaping.toml file, when the cache expires the new setting will be read.

4

Thanks @yearning-hyena

5

what if i still need to restart, due to changes in init.lua? my guess is that queues and spool would not be affected, figured this based on other conversations in the channel, i would need a confirmation for my supposition :grinning_face_with_smiling_eyes:

6

So when you shut it down it may take some time because it will be doing cleanup of inbound and outbound connections, but if allowed to do so it will not lose any messages (unless you used filesystem for the spool type and set the path to a RAM drive and the power fails ;))

7

rocksdb for spool

8

As you should.

9

So yeah, send it a restart and wait.

10

The busier it is at time of restart the longer it will take because it needs to finish all applicable timeouts on outbound messages and let inbound ones finish their current transaction.

11

and queues are running on a rust lib from what i read, so these should not be affected by kumo actual restart

12

Affected how?

13

in terms of clean

14

Yes, RocksDB is very safe in how it manages queue data, but it doesn’t run independently of the KMTA process, so KMTA still has to do its thing.

15

Worst case with a hard kill is that you may have a message that got sent to say Google, Kumo finished passing the message, but got a kill before it received the 250 ok, which means that on restart KumoMTA will re-attempt the message. That’s why sending the shutdown or restart and letting it do its thing is important.