VOTEQ...VOTES(3)
π VOTEQ...VOTES(3) π
okay bestie, sit DOWN, we're learning votequorum today and it's gonna be iconic, no cap. this one lives in the Corosync Cluster Engine Programmer's Manual, so you already know it's giving β¨ serious systems energy β¨. grab a snack, hydrate, and let's go π«Ά
πΈ NAME πΈ
votequorum_setvotes β sets the number of votes for a node. literally its whole job. one (1) task. main character behavior honestly π
π SYNOPSIS π
#include <corosync/votequorum.h>
int votequorum_setexpected(votequorum_handle_t handle, unsigned int
nodeid, int votes);
so first you gotta pull in the header with that #include <corosync/votequorum.h> line, and then the call itself is votequorum_setexpected. it takes a votequorum_handle_t handle, an unsigned int nodeid, and an int votes.
ok bestie i KNOW. the NAME section saysvotequorum_setvotesand the synopsis declaresvotequorum_setexpected. that's just what the page says, i'm not touching it, i'm just reporting the vibes π copy it exactly as written, don't get cute with it.
π¦ DESCRIPTION π¦
so votequorum_setvotes is the function you use to change how many votes a node has. that's the whole point of it. it's a glow-up for a node's vote count π
BUT β and this is the important part, listen up β you cannot use this function to change the number of node votes in a way that makes the cluster go inquorate. nope. not allowed. the function will simply not let you do that. so don't show up trying to tank your own cluster, it's not the vibe π₯
β RETURN VALUE β
this call returns the CS_OK value if it's successful. and if it's not? you get an error back instead. that's it, that's the deal β¨
π ERRORS π
here's the whole roster of what can come back at you, every single one:
CS_ERR_TRY_AGAINβ resource temporarily unavailable. it's busy, bestie, try again in a sec πCS_ERR_INVALID_PARAMβ invalid argument. something you passed in was just... not it πCS_ERR_ACCESSβ permission denied. not your house, not your rules π«CS_ERR_LIBRARYβ the connection failed. the link is not linking πCS_ERR_INTERRUPTβ system call interrupted by a signal. rude honestly πCS_ERR_NOT_SUPPORTEDβ the requested protocol/functionality not supported. it's giving "we don't do that here" πCS_ERR_MESSAGE_ERRORβ incorrect auth message received. sus message detected πCS_ERR_NO_MEMORYβ not enough memory to complete the requested task. the brain is full, no thoughts, head empty π§
π SEE ALSO π
go read these next, they're the whole friend group:
votequorum_overview(3)votequorum_initialize(3)votequorum_finalize(3)votequorum_getinfo(3)votequorum_trackstart(3)votequorum_trackstop(3)votequorum_fd_get(3)votequorum_dispatch(3)votequorum_context_set(3)votequorum_context_get(3)votequorum_setexpected(3)
and that's the page, bestie π«Ά this was the Corosync man page, dated 2026-09-04, and it's from the Corosync Man Page source. periodt πβ¨
π¦ where this page comes from
- fedora 43: corosynclib-devel 3.1.10-3.fc43 Β· BSD-3-Clause
- fedora 43: corosynclib-devel 3.1.10-3.fc43 Β· BSD-3-Clause
- fedora 44: corosynclib-devel 3.1.10-6.fc44 Β· BSD-3-Clause
- fedora 44: corosynclib-devel 3.1.10-6.fc44 Β· BSD-3-Clause
- Copyright (c) 2009,2012 Red Hat, Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms