Netty is used for communication between workers and then the LMAX disruptor queue is used to route messages between Netty and the individual executors such as the MongoSpout and KafkaBolt. AFAIK, there are not direct object references shared between executors because all executors communicate via Netty/LMAX (shuffle/fieldsGrouping) or LMAX (localIrShuffleGrouping).
--John Sent from my iPhone > On Apr 21, 2016, at 1:29 AM, Navin Ipe <[email protected]> > wrote: > > In the below code, > > public static void main(String[] cmdArgs) { > Config config = new Config(); > config.setNumWorkers(5); > MongoManager mongoManager = new MongoManager(); > > TopologyBuilder builder = new TopologyBuilder(); > builder.setSpout("someSpout", new MongoSpout(mongoManger))); > } > > Assuming there are many more spouts and blots created, I understand that each > worker will run in its own JVM, which means that it will have its own memory > space. > > Questions: > 1. So when the mongoManager reference is passed to MongoSpout, will > MongoSpout always be able to access the initialized members of mongoManager? > 2. Isn't it likely that main() runs in a different JVM and a MongoSpout will > be in another JVM? How would Storm access mongoManager? Using Netty? > 3. (optional help) I have the Storm source code. Could anyone point me to the > part that Storm does the inter-worker communication for accessing class > references? > > -- > Regards, > Navin
