[ https://issues.apache.org/jira/browse/STORM-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Li reopened STORM-3436: ----------------------------- > TupleInfo.id is not set, making debugging more difficult than it should be > -------------------------------------------------------------------------- > > Key: STORM-3436 > URL: https://issues.apache.org/jira/browse/STORM-3436 > Project: Apache Storm > Issue Type: Bug > Components: storm-client > Affects Versions: 2.0.0 > Reporter: Stig Rohde Døssing > Assignee: Stig Rohde Døssing > Priority: Major > Labels: pull-request-available > Fix For: 2.0.1 > > Time Spent: 50m > Remaining Estimate: 0h > > TupleInfo has an id field, which is supposed to contain the tuple root id. > This is printed when we enable topology debug logging, and is supposed to > make it easier to track down e.g. why a tuple timed out. > We currently don't set this field, so it's always null. The logs end up > looking like > 2019-06-29 11:26:31.990 o.a.s.e.s.SpoutExecutor > Thread-14-kafka_spout-executor[4, 4] [INFO] SPOUT Acking message null > {topic-partition=kafka-spout-test-0, offset=28, numFails=0, nullTuple=false} > The message doesn't contain the root id, and is therefore not useful for > debugging. -- This message was sent by Atlassian JIRA (v7.6.14#76016)