Dell - Internal Use - Confidential Mark, Can you give us some information like how many workers (each with 48G of RAM) you have in your cluster and how many bolts in your topology.
Tasks run on executor threads inside a worker JVM and based on how many workers you have tasks share the same JVM. You can always set the –Xms to 1G and –Xmx to 8G, this way only the workers running the memory intensive bolt will grow to 8G and shrink. This also boils down to how many workers you want to run on a server and what amount of GC pauses are tolerable to you. The number of workers you run on a server is also controlled by the number of cores you have on it in addition too, something to keep in mind. From: Mark Zang [mailto:[email protected]] Sent: Friday, May 22, 2015 12:10 PM To: [email protected] Subject: Is it supported to set different JVM options for different tasks(workers)? In a topology, some task might consumes more memories and some consumes less. So is it supported to set task level / worker level JVM options to set worker process JVM options? For example, the physical host have 48G memories. The main task prefer to use 8G memories. But the rest just need 1G or less. So it is needed to specify a -Xmx8g in workerOpt In this way, the 48G physical host can start only 6 workers. But it is risky to specify 8G memories and start more than 6 workers per physical host. Is there a best practice to config this?
