In February 2026, the Apache DolphinScheduler community maintained an active development pace. This month’s work mainly focused on improving system stability, enhancing existing features, and optimizing code quality. Community members made significant contributions in bug fixing, user experience improvements, documentation updates, and advancing important architectural decisions.
Key Highlights
1. Support for Configurable Maximum Runtime of Workflow/Task Instances
One of the most important features introduced this month is support for configurable maximum runtime for workflow and task instances (Feature-17931). Users can now set a maximum runtime for a workflow or an individual task. When the instance exceeds this time limit, the system will automatically handle it (for example, marking it as failed or canceling it). This provides stronger guarantees for resource management and preventing runaway tasks.
2. Master Node Dispatch Timeout Check Logic
To improve system robustness, timeout checking logic for task dispatch has been added to the Master node (Improvement-17795). When a Worker group does not exist or no available Workers are present, this feature can handle dispatch timeout scenarios, preventing tasks from remaining in a waiting state for a long time and improving scheduling reliability.
3. Proposal to Remove the Import/Export Feature
The community is discussing an important improvement proposal (DSIP-104) that suggests removing the import and export functionality from the project (DSIP-104). This usually indicates that the community is considering adopting more modern and reliable ways to manage and migrate workflows, such as through GitOps or other version-control-friendly approaches. This is an architectural evolution worth watching.
Fixes and Improvements
UI/UX
- Fixed the issue where the KeyCloak icon returned a 404 error (Fix-18006).
- Improved the validation logic for Spark parameters, enhancing the experience when configuring Spark tasks (Improvement-17957).
- Fixed an issue where the workflow definition list loading lock was not released when a request failed (Fix-17984).
API and Backend
- Stored Procedure Task Enhancements: This month the community focused on improving and fixing the Procedure task type. Issues with parameter passing not working (Fix-17967) and local parameters not being passed correctly (Fix-17971) were resolved, improving the stability of this task type.
- Fixed a permission issue where non-admin users could not delete their own access tokens (Fix-17995).
- Fixed missing tenant validation in workflows, strengthening multi-tenant security (Fix-17969).
- Fixed inconsistent timeout unit settings in the HTTP alert plugin (Fix-17915).
Database
- Fixed the mismatch between the INT and BIGINT types of the workflow_definition_code field in the t_ds_serial_command table (Fix-17979), ensuring database stability and data consistency.
Other Improvements
- Added support for creating Worker groups without Workers, providing more flexible resource configuration (Improvement-17926).
- Hardened the startup scripts and parameter handling for SeaTunnel tasks (Improvement-17994).
Community and Ecosystem
Documentation
- Community members fixed several spelling and wording issues in multiple README files (Doc).
- Added a section on frontend code checks in the development documentation to help new contributors better follow project standards (Doc-17913).
Code Quality and Refactoring
- Upgraded the Zookeeper dependency version to 3.8.3 (Chore).
- Upgraded the testcontainer dependency version to 1.21.4 to resolve Docker environment issues in CI (Chore).
- Refactored the datasource plugin manager and processor manager to improve code structure (Chore).
- Refactored Kubernetes task code by moving the generateK8sTaskExecutionContext method into the more specific K8sTaskParameters class, making code responsibilities clearer.
Community Governance and Continuous Integration (CI)
- Added AI usage confirmation to the PR template, reflecting the community’s attention to code contribution quality and originality (Chore).
- Updated the CI configuration so that when new commits are pushed to a PR, previous review comments automatically become outdated. This helps ensure that code reviews are always based on the latest changes, improving collaboration efficiency.
Acknowledgments to Contributors
Thanks to all community members who contributed to Apache DolphinScheduler in February (in no particular order):
- Wenjun Ruan
- xiangzihao
- yzeng1618
- Divyansh Pratap Singh
- dill
- Muhammad Asad
- huangsheng
- XpengCen
- njnu-seafish
- maomao_zero
Special thanks to Wenjun Ruan, who was very active in February and contributed numerous fixes, improvements, and code refactoring to the community.
Outlook
From the February updates, it is clear that the Apache DolphinScheduler community continues to move steadily toward becoming more stable, more user-friendly, and more powerful. In the coming months, the community is expected to continue:
- Continuously improving stability: Bug fixes and system improvements will remain a top priority.
- Advancing architectural optimization: As seen in discussions about the import/export feature, the community will keep exploring and implementing better architectural solutions.
- Focusing on user experience: Ongoing UI/UX improvements will provide users with a better operational experience.
Thanks to all developers who contributed to the DolphinScheduler community.
Note: The references in parentheses (for example, Fix-18006) correspond to Issue or Pull Request numbers on GitHub for DolphinScheduler, allowing readers to find more detailed information.
Top comments (0)