Is anyone aware of a config setting that could cause the indexing topology to stop after writing 10k messages?
I have a parser running, writing into the indexing topic. Upon restart, the indexing topology (just ES enabled for now) picks up the latest (not oldest non-committed!) messages and puts 10000 into the current index. Then it silently stops. No logs (ES, Kafka, Storm) give an indication what’s preventing it from going on. When restarting the topology, it does another round of 10k messages and stops again. Very weird. This is on a cluster build from Friday’s master and bare metal installation according to the documentation. Thanks, Christian
