[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lincoln lee updated FLINK-21799: Fix Version/s: (was: 1.19.0) > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Xintong Song >Priority: Minor > Labels: auto-deprioritized-major > Fix For: 1.20.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lincoln lee updated FLINK-21799: Fix Version/s: 1.20.0 > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Xintong Song >Priority: Minor > Labels: auto-deprioritized-major > Fix For: 1.19.0, 1.20.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-21799: Fix Version/s: 1.19.0 (was: 1.18.0) > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Xintong Song >Priority: Minor > Labels: auto-deprioritized-major > Fix For: 1.19.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-21799: - Fix Version/s: 1.18.0 (was: 1.17.0) > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Xintong Song >Priority: Minor > Labels: auto-deprioritized-major > Fix For: 1.18.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Godfrey He updated FLINK-21799: --- Fix Version/s: 1.17.0 (was: 1.16.0) > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Xintong Song >Priority: Minor > Labels: auto-deprioritized-major > Fix For: 1.17.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Gao updated FLINK-21799: Fix Version/s: 1.16.0 > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Xintong Song >Priority: Minor > Labels: auto-deprioritized-major > Fix For: 1.15.0, 1.16.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-21799: - Fix Version/s: (was: 1.14.0) 1.15.0 > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Xintong Song >Priority: Minor > Labels: auto-deprioritized-major > Fix For: 1.15.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-21799: --- Labels: auto-deprioritized-major (was: stale-major) Priority: Minor (was: Major) This issue was labeled "stale-major" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Xintong Song >Priority: Minor > Labels: auto-deprioritized-major > Fix For: 1.14.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-21799: --- Labels: stale-major (was: ) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Xintong Song >Priority: Major > Labels: stale-major > Fix For: 1.14.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-21799: - Component/s: (was: Runtime / Checkpointing) Runtime / Coordination > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Xintong Song >Assignee: Xintong Song >Priority: Major > Labels: stale-assigned > Fix For: 1.14.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-21799: - Labels: (was: stale-assigned) > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination >Reporter: Xintong Song >Assignee: Xintong Song >Priority: Major > Fix For: 1.14.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-21799: --- Labels: stale-assigned (was: ) 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 14, 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. If the "warning_label" label is not removed in 7 days, the issue will be automatically unassigned. > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Checkpointing >Reporter: Xintong Song >Assignee: Xintong Song >Priority: Major > Labels: stale-assigned > Fix For: 1.14.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-21799: - Labels: (was: stale-assigned) > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Checkpointing >Reporter: Xintong Song >Assignee: Xintong Song >Priority: Major > Fix For: 1.14.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-21799: - Fix Version/s: (was: 1.13.0) 1.14.0 > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Checkpointing >Reporter: Xintong Song >Assignee: Xintong Song >Priority: Major > Labels: stale-assigned > Fix For: 1.14.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-21799) Detect and fail explicitly on managed memory leaking
[ https://issues.apache.org/jira/browse/FLINK-21799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-21799: --- Labels: stale-assigned (was: ) > Detect and fail explicitly on managed memory leaking > > > Key: FLINK-21799 > URL: https://issues.apache.org/jira/browse/FLINK-21799 > Project: Flink > Issue Type: Improvement > Components: Runtime / Checkpointing >Reporter: Xintong Song >Assignee: Xintong Song >Priority: Major > Labels: stale-assigned > Fix For: 1.13.0 > > > As discussed in FLINK-21419, it would be helpful to fail explicitly if a > managed memory leaking is detected. > The leaking can be detected as: > * A segment being GC-ed is never freed. > * A memory manager being closed does not have all its memory released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
