[
https://issues.apache.org/jira/browse/FLINK-35603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuxin Tan updated FLINK-35603:
------------------------------
Description:
Follow up the test for https://issues.apache.org/jira/browse/FLINK-35533
In Flink 1.20, we proposed integrating Flink's Hybrid Shuffle with Apache
Celeborn through a pluggable remote tier interface. To verify this feature, you
should reference these main two steps.
1. Implement Celeborn tier.
Implement a new tier factory and tier for Celeborn.
The implement should include these APIs, including
TierFactory/TierMasterAgent/TierProducerAgent/TierConsumerAgent.
The implementations should support granular data management at the Segment
level for both client and server sides.
2.
was:
Follow up the test for https://issues.apache.org/jira/browse/FLINK-35533
In Flink 1.20, we proposed integrating Flink's Hybrid Shuffle with Apache
Celeborn through a pluggable remote tier interface. To verify this feature, you
should reference these main two steps.
1. Implement Celeborn tier.
Implement a new tier factory and tier for Celeborn.
The implement should include these APIs, including
TierFactory/TierMasterAgent/TierProducerAgent/TierConsumerAgent.
The implementations should support granular data management at the Segment
level for both client and server sides.
> Release Testing Instructions: Verify FLINK-35533(FLIP-459): Support Flink
> hybrid shuffle integration with Apache Celeborn
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-35603
> URL: https://issues.apache.org/jira/browse/FLINK-35603
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Network
> Reporter: Rui Fan
> Assignee: Yuxin Tan
> Priority: Blocker
> Labels: release-testing
> Fix For: 1.20.0
>
>
> Follow up the test for https://issues.apache.org/jira/browse/FLINK-35533
> In Flink 1.20, we proposed integrating Flink's Hybrid Shuffle with Apache
> Celeborn through a pluggable remote tier interface. To verify this feature,
> you should reference these main two steps.
> 1. Implement Celeborn tier.
> Implement a new tier factory and tier for Celeborn.
> The implement should include these APIs, including
> TierFactory/TierMasterAgent/TierProducerAgent/TierConsumerAgent.
> The implementations should support granular data management at the Segment
> level for both client and server sides.
> 2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
