apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vlad Rozov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APEXCORE-504) Possible race condition in StreamingContainerAgent.getStreamCodec()
Date Sun, 26 Mar 2017 00:12:42 GMT

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

Vlad Rozov updated APEXCORE-504:
--------------------------------
    Fix Version/s: 3.5.1

> Possible race condition in StreamingContainerAgent.getStreamCodec()
> -------------------------------------------------------------------
>
>                 Key: APEXCORE-504
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-504
>             Project: Apache Apex Core
>          Issue Type: Bug
>    Affects Versions: 3.3.0, 3.2.1, 3.4.0, 3.5.0
>            Reporter: Vlad Rozov
>            Assignee: Vlad Rozov
>             Fix For: 3.3.1, 3.2.2, 3.5.1, 3.6.0, 3.4.1
>
>
> StreamingContainerAgent.getStreamCodec() may be called from multiple RPC heartbeat processing
threads for the same inputPortMeta (for an input port of a partitioned operator) that leads
to a race condition in the following code:
> {noformat}
>       StreamCodec<?> codec = inputPortMeta.getValue(PortContext.STREAM_CODEC);
>       if (codec == null) {
>         // it cannot be this object that gets returned. Depending on this value is dangerous

>         codec = inputPortMeta.getPortObject().getStreamCodec();
>         if (codec != null) {
>           // don't create codec multiple times - it will assign a new identifier
>           inputPortMeta.getAttributes().put(PortContext.STREAM_CODEC, codec);
>         }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message