s6-rc-update has a mechanism to help people give instructions on how
to switch databases: the conversion file. However, it is a difficult
tool to use in automated scripts such as svctl, because it requires
writing a file by hand: it has been designed to help smoothen the
transition between two
On Tue, Oct 20, 2020 at 02:53:50PM +0200, Oliver Schad wrote:
> But because it could cause a production problem (think about a master
> SQL server in a high traffic situation wich kills all his caches during
> restart and maybe will be down for minutes), I think there should be a
> way to give
On Tue, 20 Oct 2020 12:30:04 +
"Laurent Bercot" wrote:
> s6-rc-update always errs on the side of caution, and if it cannot be
> certain that all the services have been brought up in the correct
> order according to the dependency chains, it restarts the necessary
> parts of the graph.
I
(Posting my answer to the mailing-list as well afterall, because I'm
not revealing any trade secrets, just general s6-rc behaviour, so it may
be useful to readers who are wondering about s6-rc-update mechanisms.)
After adding a new service to our exclusive policy package we're
observing
Hey Ansgar,
You sent your mail to the skaware mailing-list, which I don't think is
what you wanted to do. ;)
I'll answer it privately in a separate e-mail.
--
Laurent
Hi Laurent
After adding a new service to our exclusive policy package we're
observing restarts of some services (oneshots to be precise) when
updating the package on our servers, and I wanted to ask if this is
expected behavior (because I did not expect it ^_^;).
Details:
On a system where the
