This repository has been archived by the owner on Jun 6, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 548
Dshuttle integration Plan #4599
Labels
Comments
Storage How to upload dataDshuttleTo upload data, please make sure your data is immutable. Then upload your data to How to use DataBy selecting team storage, the server path will be automatically mounted to |
The Dshuttle failure pattern is
Expected behavior:
Real behavior
|
This was referenced Sep 10, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
P0: Integrate with PAI
Code freeze: 9.31 Endgame: 10.12
Deploy
1. PAI service config
2. Add alluxio.fuse into /etc/updatedb.conf
3. Expose Dshuttle API to frontend
4. Add dshuttle type in rest-server
5 Refine UI display, need @yiyione help
6. A tool to let customer preload data to dshuttleMemory high usage is cause by grpc flow-control issue, and can be mitigate by change default config. Seems 6GB~8GB for CSI is enough
Robust
1. Worker down/rejoin when running jobs P0
case: job read all data from Dshuttle/partial from Dshuttle/All from UFS.
Expected behavior:
- User job can continue running without any failure.
- Rejoined worker node can serve the request.
- Missing file will read from UFS
2. Client daemon failure when running jobs P1
- One fuse daemon failed will not affect other job running on same node
3. Worker down/rejoin when preload data P1
Expected behavior:
- Failed worker will not block uploading process
- Rejoined worker will continue serve the task
1. Consume all data from UFS
2. Consume all data from Dshuttle
3. Partial in Dshuttle
User experience
P1
The text was updated successfully, but these errors were encountered: