Stop a Server
tdkserver stop shuts down a running instance's services and leaves everything
else in place. The instance stays registered, its configuration is untouched, and
the tables and function code it holds survive, so a later
start picks up where the stop left off.
tdkserver stop --instance myinstance
The command prints the values it resolved and waits for confirmation. Pass --yes
to skip the prompt.
tdkserver status --instance myinstance
Running functions
Stopping the server stops its workers with it, so a function run in flight does not finish. Nothing partial is committed: a run only commits when every function in its execution plan succeeds, so an interrupted run leaves the tables at the version they held beforehand. Check for active work before stopping:
tdk fnrun list --status running
Picking up a configuration change
A configuration edit reaches a running instance through a restart rather than a stop:
tdkserver restart --instance myinstance
What to do next
Start a Server to bring the same instance back up, or Delete a Server to discard it.
See tdkserver stop for the full option list.