提交Apache Storm拓扑触发InvalidTopologyException问题排查

Let's break down exactly why you're hitting this InvalidTopologyException with your topology code, and how to fix it:

1. Possible Null Spout Instance #

First, look at how you're setting up your Spout:

topologyBuilder.setSpout("konnect_smstags_spout",new Konnect_SMSTags_Spout(zkConnString,topic).getKonnectSMSTagsSpout());

Apache Storm requires every Spout to be a valid, non-null implementation of ISpout. If the getKonnectSMSTagsSpout() method fails to initialize correctly (say, due to a bad ZooKeeper connection string or invalid topic name) and returns null, Storm will immediately reject your topology as invalid.

Quick Fix: Add debug logging or a null check to confirm that getKonnectSMSTagsSpout() returns a properly initialized Spout instance before passing it to setSpout().

2. Missing Emitted Stream in Your Logger Bolt #

Your summary bolt uses a globalGrouping to subscribe to the logger bolt:

topologyBuilder.setBolt("smstag_basicsummary_bolt", new SMSTag_BasicSummary_Bolt(),1).globalGrouping("smstag_logger_bolt");

Storm enforces that every Bolt (that's not directly connected to a Spout) has a valid input stream to consume. If your SMSTag_Logger_Bolt only logs tuples and never calls collector.emit() in its execute() method, there's no data stream for the summary bolt to process. This breaks the topology's valid flow and triggers the exception.

Quick Fix:

• If you intended the logger bolt to pass data downstream, make sure it calls collector.emit() with the received tuple (or a modified version of it).
• If the logger bolt doesn't need to forward data, either remove the summary bolt's dependency on it, or rewire the summary bolt to subscribe directly to the Spout if that aligns with your logic.

3. Less Common: Component Initialization Failures #

It's also possible that your Spout or Bolt classes are throwing unhandled exceptions in their constructors or prepare() methods. For example, if SMSTag_BasicSummary_Bolt can't initialize a required resource (like a database connection) during setup, Storm will flag it as an invalid component.

Quick Fix: Wrap constructor/setup logic in try-catch blocks and add detailed logging to catch initialization errors early.

内容的提问来源于stack exchange，提问作者Adarsh Trivedi