{"push_id":891141175,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"7deb0293ce0bfb29fe171d4a999fdd68b4fa6395","before":"37686391bbc796940f4b8c6244ddff2d4a362f06","commits":[{"sha":"2fbd8170bf81aa9e65bc8c7dd26cd2ae39ed3f7e","author":{"email":"872d470aa32a78f7500825688ecd953376bed386@gmail.com","name":"Erik Weathers"},"message":"allow simultaneous launching of 2+ worker processes per host\n\nOne of the logic changes in PR #65 broke the ability to simultaneously launch\nmore than 1 worker process for a given topology.  The cause of the breakage\nwas intentionally avoiding inclusion of the executor's resources into the\nExecutorInfo structure associated with the mesos tasks (storm workers).\nNotably, the avoidance is only triggered for tasks other than the 1st one\nthat potentially launches the executor.\n\nThis is problematic because the mesos-master rejects tasks whose ExecutorInfo\nisn't identical to other tasks under the same executor.  Notably, since the\nexecutor is already running for subsequent tasks, the resources that are\nadded to these subsequent tasks' ExecutorInfo aren't actually used, so there\nis no advantage in attempting to avoid their inclusion.\n\nFFR, this is the commit with that change:\n* af8c49beac04b530c33c1401c829caaa8e368a35\n\nAfter this fix I was able to instantly launch 3 workers for a topology\non the same mesos-slave host.","distinct":true,"url":"https://api.github.com/repos/mesos/storm/commits/2fbd8170bf81aa9e65bc8c7dd26cd2ae39ed3f7e"},{"sha":"7deb0293ce0bfb29fe171d4a999fdd68b4fa6395","author":{"email":"872d470aa32a78f7500825688ecd953376bed386@gmail.com","name":"Erik Weathers"},"message":"Merge pull request #78 from erikdw/allow-simultaneous-launching-of-more-than-1-worker-per-host\n\nallow simultaneous launching of 2+ worker processes per host","distinct":true,"url":"https://api.github.com/repos/mesos/storm/commits/7deb0293ce0bfb29fe171d4a999fdd68b4fa6395"}]}