Hi Jie,
A few questions:
1. How many topologies do you have running on this cluster?
2. Once the topology recovers, do the errors still happen or do they
disappear for the most part?
3. Have you noticed any worker failures on the cluster around the time
these errors happen?
-Nathan
On Tue, Aug
Thanks Dmitry. We are using Trident with transactional spout/state, and
this happens in the first 10 minutes when the topolgoy starts, and recover
itself after then. Since the topology is transactional, same messages are
replayed, so this doesn't seem a data issue, and does seem some storm bug?
If you have access to the bolt, check what fields the bolt is expecting.
You may have some coding issues when creating a Tuple for it.
Here is example of the method that defines what fields the bolt is
outputting taken from
https://storm.incubator.apache.org/documentation/Tutorial.html. The
Execu
Hi all,
We've been testing Storm for a while and have been happy so far, but this
error seems a bit unknown and concerning. One of our topologies somehow
came across this error during testing with nothing really changed, so I
have no clue how to debug it. And it seems an transient error, as the
