SLONIK_CLONE_PREPARE(7)

📦
version 2.2.11 · 4 versions
, in debian trixie, ubuntu questing

💖 CLONE PREPARE 💖

okay bestie, welcome to the slonik manual, section 7, and today's episode is all about CLONE PREPARE. pull up a chair, grab a boba, we're doing this. 🧋✨

🌸 NAME 🌸

CLONE PREPARE — the glow-up ritual where you prep for cloning a node. that's it, that's the name, short and iconic.

✨ SYNOPSIS ✨

clone prepare [ id] [ provider] [ comment]

three little optional friends, all vibing in brackets. look at them. 🫶

💅 DESCRIPTION 💅

so what are we actually doing here? we're preparing to clone a specified subscriber node. yes, the subscriber node. that one. 💅

what this command literally does is duplicate the provider node's configuration under a new node ID, and it does that in preparation for the node to be copied via standard database tools. it's giving "setting the stage so the copy actually works."

🚨 okay listen, this part is SO important, do not skip it. in order that we be certain that this new node be consistent with all nodes, you must issue a SYNC event against every node aside from the provider, and you have to wait to start copying the provider database at least until all those SYNC events have been confirmed by the provider. if you don't do this? it is possible for the clone to miss some events. and a clone that's missing events is not slaying, it's just... broken. 😭

so: sync everything else, wait for confirmation, then copy. in that order. no shortcuts. periodt. 👑

🦋 EXAMPLE 🦋

here's what it looks like in the wild, fr fr:

clone prepare (id = 33, provider = 22, comment='Clone 33');
sync (id=11);
sync (id=22);

see how we clone prepare first, then hit those sync calls? that's the choreography. don't freestyle it. 🌈

⭐ SLONIK EVENT CONFIRMATION BEHAVIOUR ⭐

cute little detail you should know: Slonik is not going to just fire this off the second you ask. it will wait until the node being cloned (the provider) is caught up with all other nodes before submitting the clone prepare command. it's patient. it's responsible. it's the main character of event ordering. 💜

🎀 VERSION INFORMATION 🎀

this absolute baddie of a command was introduced in Slony-I 2.0. vintage, but make it fashion. 🍓

that's the whole page, bestie. go forth and clone responsibly. 💖✨🦋

Slony-I 2.2.11 Documentation · 19 September 2024 — mwah, catch you in the next manpage. 🫶💅👑

📦 where this page comes from