TSCONTTHREADAFFINITYSET(3ts)

💖 TSCONTTHREADAFFINITYSET 💖

okay bestie, welcome to the Apache Traffic Server manual, section 3ts. today's main character is TSContThreadAffinitySet — the API function that lets you pick exactly which event thread your continuation gets to hang out on. no more "wherever the scheduler feels like it" energy. we're choosing. we're committing. periodt. 👑

---

✨ NAME ✨

TSContThreadAffinitySet — the TSContThreadAffinitySet API function 🎀

---

🌸 SYNOPSIS 🌸

#include <ts/ts.h>

TSReturnCode TSContThreadAffinitySet(TSCont contp, TSEventThread
ethread)

---

🦋 DESCRIPTION 🦋

So here's the vibe: you call this and you set the thread affinity of the continuation contp to ethread. like, you're basically matchmaking your continuation with a specific event thread and saying "this one. this is the one. 💅"

From then on, any future calls to TSContSchedule(), plus any TSContScheduleOnPool() calls that have the same type as ethread, will schedule the continuation on ethread — instead of yeeting it onto some arbitrary thread of that type. no cap. it's giving ✨destiny✨.

Also important, and lowkey the plot twist: TSContSchedule() and TSContScheduleEvery() will default the affinity to the calling thread when you invoke them without explicitly setting the thread affinity. so if you never call this function, the calling thread is the default bestie. 🫶

---

💫 RETURN VALUES 💫

• TS_SUCCESS — yay! 🎉 the thread affinity of continuation contp was set to ethread.
• TS_ERROR — nope. 😭 it was not.

---

👑 COPYRIGHT 👑

2026, dev@trafficserver.apache.org

---

and that's the whole page, bestie. every flag, every value, every word — untouched, just ✨glowed up✨. go set some thread affinity, you iconic thing. 🌈💜

9.2 — Feb 12, 2026 — TSCONTTHREADAFFINITYSET(3ts) 🌸 slay, bye!! 💅✨