You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Erik Toth (JIRA)" <ji...@apache.org> on 2015/04/01 18:59:52 UTC
[jira] [Created] (STORM-743) Invalid JSON produced when serializing
TaskInfo and DataPoint types
Erik Toth created STORM-743:
-------------------------------
Summary: Invalid JSON produced when serializing TaskInfo and DataPoint types
Key: STORM-743
URL: https://issues.apache.org/jira/browse/STORM-743
Project: Apache Storm
Issue Type: Bug
Affects Versions: 0.9.3
Reporter: Erik Toth
Priority: Minor
In experimenting with a pure Node.js topology I attempted to write a simple logging consumer Bolt by merely observing the `__metrics` streams from my other existing components.
In doing so I observed that the message sent to my tasks is not valid json. For example:
```
{
"comp": "changes",
"tuple": [backtype.storm.metric.api.IMetricsConsumer$TaskInfo@28b63f13,[[__emit-count = {}],[__process-latency = {}],[__receive = {read_pos=0, write_pos=1, capacity=1024, population=1}],[__ack-count = {}],[__transfer-count = {}],[__execute-latency = {}],[__fail-count = {}],[__sendqueue = {read_pos=-1, write_pos=-1, capacity=1024, population=0}],[__execute-count = {}]]],
"task":4,
"stream":"__metrics",
"id":"1702055549821416448"
}
```
This seems to be able to be tracked directly to bad JSON serialization of TaskInfo and the collection of Datapoint [1].
(Thanks!)
[1] https://github.com/nathanmarz/storm/blob/cdb116e942666973bc4eaa0df098d5bab82739e7/storm-core/src/jvm/backtype/storm/metric/api/IMetricsConsumer.java
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)