The reply-to header on list messages is the list address, so by default you will not be CC'd unless the sender specifically adds you to the cc field.
You can either subscribe to the list or periodically check the archive. -Taylor > On May 13, 2014, at 7:39 PM, Erik Weathers <[email protected]> wrote: > > Hi again. I see from the list archives that a response came in (thanks > Bobby Evans!), but I didn't receive an email, so I'm guessing Bobby didn't > send it to me, but only to the list (which I'm not subscribed to): > > > http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/201405.mbox/%3CCF979196.2CB4A%25evans%40yahoo-inc.com%3E > > Response I received: >> LocalCluster does not launch thrift, as far as I know. In this mode > calls to the ³Client² APIs become calls directly into the nimbus APIs. > > We have code that needs to create a Nimbus.Client and talk to the Nimbus. > How can I create a Nimbus.Client when using the LocalCluster? > When using a real cluster, we call: > NimbusClient.getConfiguredClient(<config-Map>).getClient(); > > Thanks! > > - Erik > > P.S., I'd greatly appreciate a reply to my email if the kind responder > would oblige. :) > > > >> On Thu, May 8, 2014 at 4:14 PM, Erik Weathers <[email protected]> wrote: >> >> hi! >> >> We're using storm-mesos and writing some stuff on top of it. >> As part of this we create a NimbusClient to interact with the Nimbus. >> >> I'm having trouble creating unit tests around this. We've successfully >> created a LocalCluster and can submit topologies into it, however I cannot >> get a NimbusClient connected. There doesn't seem to be any nimbus thrift >> port being listened to by the LocalCluster (using lsof, I don't see any >> open port to connect to). The Clojure code is pretty hard for me to read, >> but I'm guessing this means that the LocalCluster isn't set up to allow TCP >> connection to its Nimbus. Is there any way to force it to open a port (and >> tell me which one it listened on)? >> >> Thanks! >> >> - Erik >>
