Hi Keyong,
Instead of picking up a new shuffleId, can we reuse an existing shuffleId
after unregistering it? If the following plan worked, it would further
simplify the implementation:
1. Downstream tasks fail because of read failures.
2. All active downstream tasks are killed, so the shuffle
+1 (non-binding)
I checked the following things:
- signatures are good.
```
gpg --import KEYS
gpg --verify apache-celeborn-0.3.1-incubating-source.tgz.asc
gpg --verify apache-celeborn-0.3.1-incubating-bin.tgz.asc
```
- checksums are good.
```
sha512sum --check apache-celeborn-0.3.1-incubating-sou
