You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Stig Rohde Døssing (Jira)" <ji...@apache.org> on 2019/11/10 13:25:00 UTC

[jira] [Assigned] (STORM-3535) KafkaOffsetMetric is not properly synchronized

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

Stig Rohde Døssing reassigned STORM-3535:
-----------------------------------------

    Assignee: Stig Rohde Døssing

> KafkaOffsetMetric is not properly synchronized
> ----------------------------------------------
>
>                 Key: STORM-3535
>                 URL: https://issues.apache.org/jira/browse/STORM-3535
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka-client
>    Affects Versions: 2.1.0
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Major
>
> KafkaOffsetMetric.getValueAndReset runs in a different thread from the rest of the spout. It uses the KafkaConsumer from the KafkaSpout. The consumer is accessed through an unsynchronized field, and the spout may replace the consumer at any time.
> We should consider whether we can fix this, or if it would be better to give the offset metric it's own consumer.
> Also the metric accesses a number of properties in OffsetManagers, which are also not synchronized.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)