Commenting out the lines above (disabling the creation of ACLs for the
Trident-state-created Zookeeper nodes) and renaming the spout works
around the issue for me. I did have to do both: simply renaming the
spout will fail after a restart of the topology, and ACLs will already
exist for spout names
Hi Josh,
This is a known issue with trident. We are working on sending
a patch.
One workaround is to re-name the spout or comment out these lines
https://github.com/apache/storm/blob/master/storm-core/src/jvm/backtype/storm/transactional/state/TransactionalState.java#L67
http
I'm looking at the secure storm branch. Specifically, I'm working off
of the v0.9.2-incubating-security branch. I'm able to get secure Storm
working, but a Trident topology is throwing zookeeper errors. Both are
using standard Kafka spouts: the Trident topology, in particular is
using
storm.kafka.t
