apache / apache/uniffle

[FEATURE] Introduce a common BannedManager to ban the found bad application

Open
#2,261 0 comments 0 reactions 0 assignees View on GitHub
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 feature

Provide a common way to banned an app to fallback to SORT shuffle manager. The app id can be extracted from a specific spark conf.

### Motivation

_No response_

### Describe the solution

_No response_

### Additional context

_No response_

### Are you willing to submit PR?

- [X] Yes I am willing to submit a PR!

Contributor guide

Open the contributing guide

Research direction

Start by locating the shuffle-manager selection path and the Spark configuration from which the application ID should be extracted. Review how SORT shuffle manager fallback is currently selected and define the common banned-application behavior. Done means a shared BannedManager can identify the configured application and route that application to SORT shuffle manager, with tests covering the fallback.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.