[Bug] Invalid decommission operation for coordinator
- Dominant language
- Java
- Stars
- 454
- Forks
- 172
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 5
Description
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
### Search before asking
- [x] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and found no similar issues.
### Describe the bug
From the code base, the decommisioning server status won't be reacted in coordinator side.
### Affects Version(s)
master
### Uniffle Server Log Output
```logtalk
```
### Uniffle Engine Log Output
```logtalk
```
### Uniffle Server Configurations
```yaml
```
### Uniffle Engine Configurations
```yaml
```
### Additional context
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Contributor guide
Research direction
Start by tracing how the coordinator handles the decommissioning server status, using the coordinator-side decommission operation described in the issue as the entry point. Reproduce the reported behavior on master and identify the missing reaction; done means the coordinator correctly responds when a server is decommissioned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100