Hello, The way storm is behaving when i am using isolation scheduler seems a strange to me. I have 6 machines and i have configured two topologies( a, b) in storm.yaml to use 2 machines each so 2 machines will be used by all the other topologies.
i have "a" already running and along with it another topology "c" also running each taking 2 machines. There are 2 machines still free. When i deploy "b" i often see storm moving topology "c" to the free machines and deploying "b" where "c" was running even though there were free machines. why does this happen ? can we prevent this ? regards, anishek
