Search before asking
Linkis Component
Description
When an Entrance instance's labels are modified through the InstanceLabelService, other Entrance instances are not notified of the change. This causes stale Group cache information, leading to incorrect user task concurrency calculations since other instances still use the old label-based concurrency settings.
Steps to reproduce
- Start multiple Entrance instances
- Modify an Entrance instance's labels through the InstanceLabelService API
- Check other Entrance instances
- Their local Group cache is not updated, causing incorrect concurrency calculations
Expected behavior
When an Entrance instance's labels are modified, all other Entrance instances should be notified to clear their local Group cache, ensuring that subsequent task submissions use the updated label-based concurrency settings.
Your environment
- Linkis version used: 2.0.0
- Environment name and version:
Anything else
This change adds:
- Broadcast trigger in InstanceRestful when Entrance labels are updated
- Move EntranceGroupCacheClearBroadcast from entrance to protocol module for better module organization
- Configuration options to enable/disable the broadcast feature
- Exception handling to ensure broadcast failures don't affect label updates
Are you willing to submit a PR?
Search before asking
Linkis Component
Description
When an Entrance instance's labels are modified through the InstanceLabelService, other Entrance instances are not notified of the change. This causes stale Group cache information, leading to incorrect user task concurrency calculations since other instances still use the old label-based concurrency settings.
Steps to reproduce
Expected behavior
When an Entrance instance's labels are modified, all other Entrance instances should be notified to clear their local Group cache, ensuring that subsequent task submissions use the updated label-based concurrency settings.
Your environment
Anything else
This change adds:
Are you willing to submit a PR?