[Improvement] [tez] Optimize tez client delivery configuration #983
Comments
zhengchenyu
added a commit
to zhengchenyu/incubator-uniffle
that referenced
this issue
Jun 30, 2023
zhengchenyu
added a commit
to zhengchenyu/incubator-uniffle
that referenced
this issue
Jul 3, 2023
zhengchenyu
added a commit
to zhengchenyu/incubator-uniffle
that referenced
this issue
Jul 3, 2023
This was referenced Jul 3, 2023
jerqi
pushed a commit
that referenced
this issue
Jul 4, 2023
…985) ### What changes were proposed in this pull request? Three improvement about configuration will be done in this issue. - 1 For now, tez client use rss_conf.xml to delivery configuration. As #966 is applied, we can delivery configuration by edge conf. - 2 delivery dynamic configuration from coordinator, then override the tez client configuration. - 3 delivery configuration from client side. ### Why are the changes needed? - 1. rss_conf.xml is unnecessary. - 2. dynamic configuration from coordinator are not applied. - 3. config in client side can not delivery to input/ouput. ### How was this patch tested? integration test, unit test, test in yarn cluster, test in tez local mode.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code of Conduct
Search before asking
What would you like to be improved?
Three improvement about configuration will be done in this issue.
1 For now, tez client use rss_conf.xml to delivery configuration. As #966 is applied, we can delivery configuration by edge conf.
2 delivery dynamic configuration from shuffle server, then override the tez client configuration.
3 delivery configuration from client side.
How should we improve?
No response
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: