[jira] [Resolved] (STORM-1848) NotSerializableException when using storm-kafka spout with event logging

["P. Taylor Goetz (JIRA)" <ji...@apache.org>]

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

P. Taylor Goetz resolved STORM-1848.
------------------------------------
    Resolution: Fixed

[~Srdo] Thanks, merged to master, 1.x-branch and 1.0.x-branch.

> NotSerializableException when using storm-kafka spout with event logging
> ------------------------------------------------------------------------
>
>                 Key: STORM-1848
>                 URL: https://issues.apache.org/jira/browse/STORM-1848
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka
>    Affects Versions: 2.0.0, 1.0.1
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Minor
>             Fix For: 2.0.0, 1.0.2, 1.1.0
>
>
> We deployed a topology to multiple workers and set topology.eventlogger.executors to be identical to the number of workers. When the debug button in Storm UI is pressed, the spout will start throwing NotSerializableExceptions.
> java.lang.RuntimeException: java.lang.RuntimeException: java.io.NotSerializableException: org.apache.storm.kafka.PartitionManager$KafkaMessageId at org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:452) at (snip)
> KafkaMessageId should be made serializable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)