MCP Academy · 课时

干净关闭与资源释放

服务器停止时关闭连接池和文件。

干净关闭与资源释放 是 CoddyKit 上的免费 MCP Academy 课时。这是第 4 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 MCP Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 MCP Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Why Shutdown Matters

Open connections that are never closed leak resources: sockets pile up, pools stay reserved, and databases stay busy.

Teardown Lives After Yield

Everything after yield in your lifespan is shutdown code, running when the server is told to stop.

async def lifespan(server):
    db = await connect()
    yield {"db": db}
    await db.close()

Close What You Opened

The golden rule: for every resource you opened in startup, add a matching close in teardown so nothing is left dangling.

try / finally Guarantees It

Wrap the yield in try / finally so cleanup still runs even if a request crashes mid-flight.

async def lifespan(server):
    db = await connect()
    try:
        yield {"db": db}
    finally:
        await db.close()

Drain In-Flight Work

A graceful stop lets in-flight tool calls finish before tearing down, instead of yanking the rug out from under them.

Flush Before You Close

Some clients buffer data, so flush pending writes before closing to avoid losing the last bytes you sent.

Close in Reverse Order

Tear things down in reverse of how you built them, so a thing is never closed while something depending on it is alive.

Don't Hang on Exit

Guard slow cleanup with a timeout so a stuck connection cannot block your whole server from ever shutting down.

Idempotent Cleanup

Make teardown idempotent: closing something twice should be harmless, since shutdown can be triggered more than once.

Log the Shutdown Path

A short log line per closed resource turns a silent exit into something you can actually debug when things go wrong.

Context Managers Do It For You

Wrapping clients in async with auto-closes them, letting Python handle release so you write less manual cleanup.

async def lifespan(server):
    async with connect() as db:
        yield {"db": db}

Quick Check

Where does a lifespan put code that releases resources?

Recap: Clean Shutdown

You release resources after yield, guard it with try/finally, close in reverse, and avoid hangs. Your server now boots and stops cleanly. ✅

常见问题解答

「干净关闭与资源释放」课时是免费的吗？

是的 — 「干净关闭与资源释放」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 MCP Academy 课程的其余内容，请升级到 CoddyKit PRO。 MCP Academy 课程共包含 4 节课。

「干净关闭与资源释放」这节课中我会学到什么？

服务器停止时关闭连接池和文件。你通过在浏览器中直接运行的动手代码来练习 MCP Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 MCP Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 MCP Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 4 节课，共 4 节。

「干净关闭与资源释放」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 MCP Academy 课中编写并运行代码吗？

能。每节 MCP Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 MCP Academy