[jira] [Updated] (FLINK-23928) Test the buffer debloating

2021-09-28 Thread Xintong Song (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-23928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xintong Song updated FLINK-23928:
-
Fix Version/s: (was: 1.14.0)
   1.15.0

> 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.15.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)


[jira] [Updated] (FLINK-23928) Test the buffer debloating

2021-09-24 Thread Flink Jira Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-23928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-23928:
---
Labels: release-testing stale-assigned  (was: release-testing)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it.


> 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)


[jira] [Updated] (FLINK-23928) Test the buffer debloating

2021-08-23 Thread Anton Kalashnikov (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-23928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Kalashnikov updated FLINK-23928:
--
Fix Version/s: 1.14.0

> 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
>Priority: Major
>  Labels: release-testing
> 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)


[jira] [Updated] (FLINK-23928) Test the buffer debloating

2021-08-23 Thread Anton Kalashnikov (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-23928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Kalashnikov updated FLINK-23928:
--
Labels: release-testing  (was: )

> 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
>Priority: Major
>  Labels: release-testing
>
> # {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)