[jira] [Updated] (FLINK-26967) Fix race condition in CopyOnWriteStateMap
[ https://issues.apache.org/jira/browse/FLINK-26967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weijie Guo updated FLINK-26967: --- Fix Version/s: 2.0.0 (was: 1.20.0) > Fix race condition in CopyOnWriteStateMap > - > > Key: FLINK-26967 > URL: https://issues.apache.org/jira/browse/FLINK-26967 > Project: Flink > Issue Type: Sub-task > Components: Runtime / State Backends >Reporter: Roman Khachatryan >Assignee: Roman Khachatryan >Priority: Major > Labels: pull-request-available, stale-assigned > Fix For: 2.0.0 > > > Currently, handling chained entry on copy-on-write uses object > identity to find the wanted entry in the chain. However, if > the same method is running concurrently, the object in the chain > can be replaced by its copy; the condition will never be met and > the chain end will be reached, causing an NPE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26967) Fix race condition in CopyOnWriteStateMap
[ https://issues.apache.org/jira/browse/FLINK-26967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lincoln lee updated FLINK-26967: Fix Version/s: 1.20.0 (was: 1.19.0) > Fix race condition in CopyOnWriteStateMap > - > > Key: FLINK-26967 > URL: https://issues.apache.org/jira/browse/FLINK-26967 > Project: Flink > Issue Type: Sub-task > Components: Runtime / State Backends >Reporter: Roman Khachatryan >Assignee: Roman Khachatryan >Priority: Major > Labels: pull-request-available, stale-assigned > Fix For: 1.20.0 > > > Currently, handling chained entry on copy-on-write uses object > identity to find the wanted entry in the chain. However, if > the same method is running concurrently, the object in the chain > can be replaced by its copy; the condition will never be met and > the chain end will be reached, causing an NPE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26967) Fix race condition in CopyOnWriteStateMap
[ https://issues.apache.org/jira/browse/FLINK-26967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-26967: Fix Version/s: 1.19.0 (was: 1.18.0) > Fix race condition in CopyOnWriteStateMap > - > > Key: FLINK-26967 > URL: https://issues.apache.org/jira/browse/FLINK-26967 > Project: Flink > Issue Type: Sub-task > Components: Runtime / State Backends >Reporter: Roman Khachatryan >Assignee: Roman Khachatryan >Priority: Major > Labels: pull-request-available, stale-assigned > Fix For: 1.19.0 > > > Currently, handling chained entry on copy-on-write uses object > identity to find the wanted entry in the chain. However, if > the same method is running concurrently, the object in the chain > can be replaced by its copy; the condition will never be met and > the chain end will be reached, causing an NPE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26967) Fix race condition in CopyOnWriteStateMap
[ https://issues.apache.org/jira/browse/FLINK-26967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-26967: - Fix Version/s: 1.18.0 (was: 1.17.0) > Fix race condition in CopyOnWriteStateMap > - > > Key: FLINK-26967 > URL: https://issues.apache.org/jira/browse/FLINK-26967 > Project: Flink > Issue Type: Sub-task > Components: Runtime / State Backends >Reporter: Roman Khachatryan >Assignee: Roman Khachatryan >Priority: Major > Labels: pull-request-available, stale-assigned > Fix For: 1.18.0 > > > Currently, handling chained entry on copy-on-write uses object > identity to find the wanted entry in the chain. However, if > the same method is running concurrently, the object in the chain > can be replaced by its copy; the condition will never be met and > the chain end will be reached, causing an NPE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26967) Fix race condition in CopyOnWriteStateMap
[ https://issues.apache.org/jira/browse/FLINK-26967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xingbo Huang updated FLINK-26967: - Fix Version/s: 1.17.0 (was: 1.16.0) > Fix race condition in CopyOnWriteStateMap > - > > Key: FLINK-26967 > URL: https://issues.apache.org/jira/browse/FLINK-26967 > Project: Flink > Issue Type: Sub-task > Components: Runtime / State Backends >Reporter: Roman Khachatryan >Assignee: Roman Khachatryan >Priority: Major > Labels: pull-request-available, stale-assigned > Fix For: 1.17.0 > > > Currently, handling chained entry on copy-on-write uses object > identity to find the wanted entry in the chain. However, if > the same method is running concurrently, the object in the chain > can be replaced by its copy; the condition will never be met and > the chain end will be reached, causing an NPE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26967) Fix race condition in CopyOnWriteStateMap
[ https://issues.apache.org/jira/browse/FLINK-26967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-26967: --- Labels: pull-request-available stale-assigned (was: pull-request-available) 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. > Fix race condition in CopyOnWriteStateMap > - > > Key: FLINK-26967 > URL: https://issues.apache.org/jira/browse/FLINK-26967 > Project: Flink > Issue Type: Sub-task > Components: Runtime / State Backends >Reporter: Roman Khachatryan >Assignee: Roman Khachatryan >Priority: Major > Labels: pull-request-available, stale-assigned > Fix For: 1.16.0 > > > Currently, handling chained entry on copy-on-write uses object > identity to find the wanted entry in the chain. However, if > the same method is running concurrently, the object in the chain > can be replaced by its copy; the condition will never be met and > the chain end will be reached, causing an NPE. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-26967) Fix race condition in CopyOnWriteStateMap
[ https://issues.apache.org/jira/browse/FLINK-26967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-26967: --- Labels: pull-request-available (was: ) > Fix race condition in CopyOnWriteStateMap > - > > Key: FLINK-26967 > URL: https://issues.apache.org/jira/browse/FLINK-26967 > Project: Flink > Issue Type: Sub-task > Components: Runtime / State Backends >Reporter: Roman Khachatryan >Priority: Major > Labels: pull-request-available > Fix For: 1.16.0 > > > Currently, handling chained entry on copy-on-write uses object > identity to find the wanted entry in the chain. However, if > the same method is running concurrently, the object in the chain > can be replaced by its copy; the condition will never be met and > the chain end will be reached, causing an NPE. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-26967) Fix race condition in CopyOnWriteStateMap
[ https://issues.apache.org/jira/browse/FLINK-26967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Khachatryan updated FLINK-26967: -- Description: Currently, handling chained entry on copy-on-write uses object identity to find the wanted entry in the chain. However, if the same method is running concurrently, the object in the chain can be replaced by its copy; the condition will never be met and the chain end will be reached, causing an NPE. > Fix race condition in CopyOnWriteStateMap > - > > Key: FLINK-26967 > URL: https://issues.apache.org/jira/browse/FLINK-26967 > Project: Flink > Issue Type: Sub-task > Components: Runtime / State Backends >Reporter: Roman Khachatryan >Priority: Major > Fix For: 1.16.0 > > > Currently, handling chained entry on copy-on-write uses object > identity to find the wanted entry in the chain. However, if > the same method is running concurrently, the object in the chain > can be replaced by its copy; the condition will never be met and > the chain end will be reached, causing an NPE. -- This message was sent by Atlassian Jira (v8.20.1#820001)
