A developer must always stop all running server instances before starting a new one. Only one server instance should ever be active at a time. Failing to do so creates 'zombie' instances that serve old code.
By Pawan Nayar · from the LLOS AI Learning record
A developer must always stop all running server instances before starting a new one.
Only one server instance should ever be active at a time. Failing to do so creates 'zombie' instances that serve old code.
Before starting a server, a developer must kill all existing instances. After killing, the developer must check that no instances are running. Then, the developer starts exactly one new instance. Finally, the developer must confirm that only one instance is active.
A developer changes code on a server. The developer starts a new server instance without stopping the old one. Now, two server instances are running. When a user makes a request, there is a chance the old server instance will respond with outdated information.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
A developer must always restart the server after any file change. The developer should never tell a user to run the server.
A 'zombie' process is an old program that is still running. It holds open network connections.
When an AI model starts a program, the new program is linked to the AI model's process. If the AI model's process closes, the program it started will also close.
A developer must restart the server immediately after changing any server file. The developer must kill the server by its port number.
A developer must always stop all running server instances before starting a new one. Only one server instance should ever be active at a time. Failing to do so creates 'zombie' instances that serve old code.