SLONIK_RESTART_NODE(7)

πŸ“¦
version 2.2.11 Β· 4 versions
, in debian trixie, ubuntu questing

πŸ’– SLONIK RESTART NODE πŸ’–

okay bestie, so this is the RESTART NODE page from the Slony-I docs β€” specifically the Slony-I 2.2.11 Documentation era, if you're keeping receipts. It lives in the SLONIK_RESTART_NODE(7) section of the manual, and it's literally just one command with one tiny option. Short page, big energy. Let's go. πŸ¦‹


✨ NAME ✨

RESTART NODE β€” restart a Slony-I node, bestie. That's the whole vibe. πŸ‘‘


✨ SYNOPSIS ✨

RESTART NODE options;

✨ DESCRIPTION ✨

So what does it do? It makes the replication daemon (that's the slon process, if you didn't know, and now you do 🫢) on the node you point at shut itself down and restart itself. Eventually. When it's running. Hence "eventually running replication daemon" β€” ngl that phrasing is a whole mood.

Now here's the tea: theoretically this command should be obsolete. Like, retired. Living its best cottagecore life. But in practice? TCP timeouts can drag their feet and delay critical configuration changes from actually happening β€” specifically in the case where a former forwarding node failed and needs to be bypassed by subscribers. So yeah, it still earns its keep sometimes. πŸ’…

the one and only option

  • ID = ival β€” the Node ID of the node you want to restart. That's it. That's the option list. Iconic minimalism. ✨

✨ EXAMPLE ✨

RESTART NODE ( ID = 2 );

no cap, that's the entire example. ate and left no crumbs. πŸ“


✨ LOCKING BEHAVIOUR ✨

Good news: no application-visible locking should take place. So nobody's out here getting blocked by this. slay. πŸŽ€


✨ SLONIK EVENT CONFIRMATION BEHAVIOUR ✨

Also important, also chill: Slonik does not wait for event confirmations before performing this command. It just sends it and moves on. main character energy, fr fr. πŸ’«


✨ VERSION INFORMATION ✨

  • This command was introduced in Slony-I 1.0 🌈
  • Frequent use became unnecessary as of version 1.0.5 βœ…
  • But β€” there are, however, occasional cases where it is necessary to interrupt a slon process, and this command lets you do that scripted via slonik. So it stays in the toolbox. πŸ’ͺ

πŸ’€ lowkey a "should be deprecated but isn't" situation, and honestly? relatable. keep it in your back pocket for the weird days, bestie.

that's the whole page, you understood it, I'm so proud of you πŸ₯Ή this was SLONIK RESTART NODE(7) from the Slony-I 2.2.11 Documentation, dated 19 September 2024. mwah πŸ’‹ go restart a node responsibly, ily, bye πŸ¦‹πŸ’–βœ¨

πŸ“¦ where this page comes from