Feature Request: Implement True “Stop Sync” Behavior

[Ramanathan (ramanathanv)]

Summary

Improve the "Stop Sync" action so that it reliably terminates the sync job immediately.

Motivation / Use Case

Currently, “Stop” waits for the connector to exit gracefully. For large reads, this may take a long time, and users cannot reclaim system resources or prevent further load on their data sources.

A robust stop mechanism is needed when:

• Source rate limits are hit
• ETL Windows close
• Critical system load spikes
• A misconfigured sync needs an urgent shutdown

Proposed Behavior

• Force termination of source/destination container processes
• Emit partial state where safe
• Ensure worker cleanup with no orphaned processes

Community Benefit

• Increases control and safety for operations teams
• Prevents runaway jobs from causing outages
• Aligns Airbyte with operational expectations of other data movement tools

Willingness to Contribute

We are ready to contribute the implementation for this feature and can start development once maintainers confirm the direction and any design constraints.