Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-30198

Support AdaptiveBatchScheduler to set per-task size for reducer task

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Runtime / Coordination
    • None

    Description

      When we use AdaptiveBatchScheduler in our case, we found that it can work well in most case, but there is a limit that, there is only one global parameter for per task data size by jobmanager.adaptive-batch-scheduler.avg-data-volume-per-task.

      However, in a map-reduce architecture, the reducer tasks are usually have more complex computation logic such as aggregate/sort/join operators. So I think it will be nicer if we can set the reducer and mapper task's data size per task individually.

      Then, how to distinguish the reducer task?
      IMO, we can let the parallelism decider know whether the vertex have a hash edge inputs. If yes, it should be a reducer task.

      Attachments

        Activity

          People

            Unassigned Unassigned
            aitozi WenJun Min
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: