Thanks for taking the time to answer my dumb question! I missed that. From: Paul Poulosky <[email protected]> Reply-To: "[email protected]" <[email protected]>, Paul Poulosky <[email protected]> Date: Monday, May 8, 2017 at 9:31 AM To: "[email protected]" <[email protected]> Subject: Re: Passing a JVM variable to a spout (or bolt)
Use the topology.worker.childopts setting to pass in jvm arguments On Monday, May 8, 2017 8:09 AM, "Hannum, Daniel" <[email protected]> wrote: Hi, I see a lot of conflicting into online about this, so hopefully the experts can help. I have a secure KafkaSpout (version 1.1.0 of both Storm and storm-kafka-client) that can’t find it’s jaas.conf. The cluster itself is secure, has jaas.conf, all of that works fine. I think what I need is to be able to pass in a –D JVM parameter into a spout to point it to the jaas.conf file, but I don’t see how to do it. If I print java.security.auth.login.config from inside my spout, it’s null. supervisor.childopts does not work. I also see that Flux exists, but that looks like it’s for sending application properties, not JVM properties. It’s also possible that I’m just using KafkaSpout wrong. I see this page https://github.com/apache/storm/blob/master/docs/storm-kafka-client.md<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_storm_blob_master_docs_storm-2Dkafka-2Dclient.md&d=DwMFaQ&c=2Nw3fMGo2X8W9N0cgJ8QEE6dJUdSW43Zo0sycqQq3H0&r=qUxrE20KiMOUmgAziv_enaLH7wvWTKTNI8fz4O6YsA0&m=fZweREqdWZ3RjLUOj9hHPSB-bxylWvlLGwZL9DtUXzw&s=hkCTUFJU35ZNwxvkZrXdYgz_XMb0oj3RRkWQiisKzf4&e=> But it doesn’t say how to read from a secure topic, so I’m troubleshooting myself and missing jaas.conf is the first problem I see. Thanks for any help you can give. Dan
