[
https://issues.apache.org/jira/browse/FLINK-23928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Nowojski closed FLINK-23928.
----------------------------------
Fix Version/s: (was: 1.15.0)
1.14.0
Resolution: Fixed
> Test the buffer debloating
> --------------------------
>
> Key: FLINK-23928
> URL: https://issues.apache.org/jira/browse/FLINK-23928
> Project: Flink
> Issue Type: Sub-task
> Reporter: Anton Kalashnikov
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: release-testing, stale-assigned
> Fix For: 1.14.0
>
>
> # {color:#6a8759}Configure the buffer debloat by setting
> `taskmanager.network.memory.buffer-debloat.enabled` to true{color}
> # {color:#6a8759}Start the job with a long checkpoint time{color}
> # {color:#6a8759}Check the alignment time for each subtask it should be near
> taskmanager.network.memory.buffer-debloat.target{color}
> # {color:#6a8759}Check the checkpoint time it should be near taskCount *
> taskmanager.network.memory.buffer-debloat.target{color}
> # {color:#6a8759}Try to change
> taskmanager.network.memory.buffer-debloat.target. Checkponint time should be
> changed correspondetly.{color}
> # {color:#6a8759}Check metrics
> {color}{color:#6a8759}estimatedTimeToConsumerBuffersMs and
> {color}{color:#6a8759}debloatedBufferSize which also should depend on the
> current debloat configuration.
> {color}
> {color:#6a8759} {color}
> {color:#6a8759}Other configuration which can be changed for test.{color}
> * {color:#6a8759}taskmanager.memory.min-segment-size(if this would be equal
> to taskmanager.memory.segment-size then the behaviour should be same as with
> disabled buffer debloat)
> {color}
> * {color:#6a8759}taskmanager.network.memory.buffer-debloat.period{color}
> * {color:#6a8759}taskmanager.network.memory.buffer-debloat.samples{color}
> *
> {color:#6a8759}taskmanager.network.memory.buffer-debloat.threshold-percentages{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
