Thanks Matt! I was wondering if something like that was possible. I think the way Azure Event hub software works it would be impossible to change this. They manage the threads and they are long running, so, as you say, they never release the first thread that starts them up. It would take a rewrite of the Ehub listener logic to fix it. Thanks for clearing this up! ... View more

Thanks for the reply, Matt. However, I am not sure you read my post entirely. The ConsumeAzureEventHub does not seem to EVER stop pumping more messages in to the queue. Could it be written incorrectly? We have it set to 10,000 and have never seen it stop rising. ... View more

We are seeing the same thing specifically with the ConsumeAzureEventHub processor. It seems to completely ignore either the size or number settings. A simple PutFile works, but not this one. We have seen it go to >1,000,000 and over a 1 gig in size. ... View more

The Microsoft EHub has been fixed in the 2.0.0 version of Storm. Yes! ... View more

The excitement was almost palpable when we found this page. We have a bug where all looks good but SOMETIMES our topology fails everything with a timeout. So in went the topology.eventlogger.executors: 1 and with excitement we hit the "DEBUG" button. Much to our surprise, MessageId is not serializable: java.lang.RuntimeException: java.lang.RuntimeException: java.io.NotSerializableException: org.apache.storm.eventhubs.spout.MessageId at org.apache.storm.utils.DisruptorQueue.consumeBatchToCursor(DisruptorQueue.java:464) at org.apache.storm.utils.DisruptorQueue.consumeBatchWhenAvailable(DisruptorQueue.java:430) at We are using Microsoft EHubs and their messageId is not Serializeable. So I have two questions: 1. Could we get this fixed? 2. How can anyone be using this? ... View more