[STORM-3436] TupleInfo.id is not set, making debugging more difficult than it should be

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.1.0
• Component/s: storm-client
• Labels: pull-request-available
• Assignee: Stig Rohde Døssing
• Reporter: Stig Rohde Døssing
• Created: 29/Jun/19 09:45
• Updated: 10/Aug/19 22:20
• Resolved: 10/Aug/19 22:20

Description

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.

Issue Links

• links to: GitHub Pull Request #3052