Inside DolphinScheduler’s May 2026 Release: Better Failover, Stronger Security, and More Reliable Plugins

2. More Rigorous Authorization for Critical APIs

Project-level authorization checks have been added to APIs such as view-gantt, view-variables, and trigger workflow.

This makes the permission model more intuitive: users without proper authorization should not be able to access these resources.

Related PR:

4. Improved Dependency Conflict Management for Task Plugins

Plugins such as AliyunServerlessSpark previously suffered from dependency conflicts that could lead to ClassNotFound or compatibility issues.

Enhancements to dependency management and exception handling improve overall plugin reliability.

Related PR:

6. More Flexible Region and Endpoint Support for AWS S3 Remote Logs

Users relying on S3-compatible storage services or private endpoints now have greater flexibility when configuring regions and endpoints.

This reduces troubleshooting time for connectivity issues caused by storage configuration differences.

Related PR:

Author: @ruanwenjun

Base/Head: dev ← dev_wenjun_fix18197

Diff Stats: +171 / -10

Background and Challenges

Master failover relies on distributed locks to ensure that failover for a given address is not executed concurrently.

If lock release logic is incorrect, lock nodes may leak, preventing future failover operations and leaving the cluster unable to resume scheduling after failures.

Design and Implementation

The lock acquisition interface was redesigned to return an AutoCloseable handle.

Using try-with-resources guarantees symmetric acquire/release behavior.

Additionally, callers now retain the exact lock path, preventing subtle mistakes such as releasing parent paths.

Suggested Metrics

Simulate failover storms in a three-Master cluster by repeatedly issuing kill -9 and automatic restarts.

Compare:

• Failover success rate


• Mean Time To Recovery (MTTR)


• Failover thread blocking duration

Registry lock node count should also be monitored, as lock leaks accumulate over time.

Compatibility and Rollback

Interface signature changes may affect callers.

Rollback is straightforward but requires cleanup of leaked lock nodes to prevent continued service disruption.

Author: @ruanwenjun

Base/Head: dev ← dev_wenjun_fixCvePermissionCheck

Diff Stats: +321 / -16

Background and Challenges

Workflow APIs without project-level authorization checks can create privilege escalation risks.

In multi-tenant enterprise environments, this becomes a serious security concern.

Design and Implementation

Authorization validation was added to:

• view-gantt


• view-variables


• trigger workflow

Permission checks are enforced consistently through Controller and Service layers.

Suggested Validation

Benchmark authorization overhead before and after implementation.

Security regression tests should include cross-project access attempts.

Best Practices

Enterprise users should enable stricter tenant isolation policies and audit sensitive API operations.

Author: @leocook

Base/Head: dev ← fix-18201-remoteshell-npe

Diff Stats: +34 / -29

Background and Challenges

RemoteShell tasks are commonly used for operations and integration workloads.

Network interruptions, command output handling differences, and SSH channel inconsistencies can easily lead to NPEs and incomplete logs.

Design and Implementation

Input/output stream handling for SSH channels was improved to eliminate null pointer scenarios.

Exception handling paths were also enhanced to preserve root-cause information.

Suggested Validation

Inject failures such as:

• Remote disconnections


• Empty output streams


• Immediate command termination

Execute 1,000 test runs and compare:

• NPE occurrence rates


• Log completeness

Risks and Rollback

Changes are isolated to the plugin layer and are relatively easy to revert.

Regression tests should continue covering:

• Empty output


• Large output


• Non-zero exit codes

4. [Fix-18177][Task Plugin] Fix AliyunServerlessSpark plugin dependency conflicts and improve exception handling (#18180)

• Link:
  


• Author: @SbloodyS


• Base/Head: dev ← ut_performance_optimize


• Diff Stats: +22 / -6

Background and Challenges

Slow, flaky, or frequently skipped tests delay problem detection until production deployment.

Testing infrastructure directly impacts community development speed and software quality.

Design and Implementation

Unit test execution and CI configurations were optimized.

Temporary safeguards were also introduced to maintain CI stability during environmental issues.

Suggested Validation

Compare:

• Total CI duration


• Number of executed unit tests


• Percentage of skipped tests


• Flaky test rerun counts

Risks and Rollback

Temporary test disablement should always include a documented recovery plan.

Conditions for re-enabling tests should be tracked through issues and PRs.

Appendix

• PR #18204:
  


• PR #18206:
  


• PR #18205:
  


• PR #18209:
  


• PR #18212:
  


• PR #18214:
  


• PR #18218:
  


• PR #18227:
  


• PR #18240:
  


• PR #18228:
  


• PR #18232:
  


• PR #18230:
  


• PR #18242:
  


• PR #18233:
  


• PR #18250:
  


• PR #18252:
  


• PR #18270:
  


• PR #18258:
  


• PR #18260:
  


• PR #18256:
  


• PR #18262:
  


• PR #18254:
  


• PR #18284:
  


• PR #18268:
  


• PR #18300: