zhuzhurk commented on PR #25647:
URL: https://github.com/apache/flink/pull/25647#issuecomment-2477797783

   > Thanks @zhuzhurk @1996fanrui for the comments.
   > 
   > Please let me to synchronize the background information and introduce the 
reasons for this change.
   > 
   > The feature freeze for version 2.0 will take place at the end of November 
2024.
   > 
   > > Does you mean that the balance of Slot to TM[1] is not planned to be 
supported in Flink 2.0?
   > 
   > We expect to release this complete feature in 2.0 ideally but I estimate 
that the two core PRs at the TaskManager level may face some risks based on the 
current progress,
   > 
   > * [[FLINK-33391][runtime] Support tasks balancing at TM level for Adaptive 
Scheduler. #25517](https://github.com/apache/flink/pull/25517) TM level 
balancing for AdaptiveSheduler)
   > * [[FLINK-33387][runtime] Introduce the abstraction and the interface 
about loading #25174](https://github.com/apache/flink/pull/25174) TM level 
balancing for DefaultSheduler)
   > 
   > Meanwhile, for FLIP-370,
   > 
   > * enabling the switch to support slot-level balancing could address a 
significant portion of the tasks skew issues.
   > * The solutions for these two PRs are already determined and are currently 
awaiting review.
   >   
   >   * [[FLINK-35966][runtime] Introduce the TASKS for 
TaskManagerLoadBalanceMode enum 
#25647](https://github.com/apache/flink/pull/25647)
   >   * [[FLINK-33389][runtime] Support tasks balancing at slot level for 
Adaptive Scheduler #25504](https://github.com/apache/flink/pull/25504)
   > 
   > Therefore, I'd like to attempt to first support the slot-level balancing 
for the two schedulers.
   > 
   > Please let me know what's your opinion~ Thx!
   
   > The feature freeze for version 2.0 will take place at the end of November 
2024
   The feature freeze date has been postponed to 2025-01-13[1]. Will it give 
enough time to complete the FLIP?
   
   [1] [DISCUSS] Feature Freeze for Flink 2.0 - Jan 13


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to