GitHub user nickpan47 opened a pull request:
https://github.com/apache/samza/pull/228
SAMZA-1334: fix pre-condition for ContainerAllocator to work properly
We have observed issues when the LocalityManager reports the container
locality mapping while the host-affinity is disabled in ContainerAllocator, in
which the ContainerAllocator failed to release extra containers.
Hence, fix is in the form of make sure the pre-condition is met for the
ContainerAllocator w/o host-affinity: the localityMap from the JobModel should
contain no preferred host info.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickpan47/samza SAMZA-1334
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/samza/pull/228.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #228
----
commit f76fff14d17f9c99dcfaa3d065f90bb5a656c705
Author: Yi Pan (Data Infrastructure) <[email protected]>
Date: 2017-06-15T17:26:15Z
WIP: SAMZA-1334 fix
commit ad3320fc66f49c5c2637b8e0dd38cf129b486f66
Author: Yi Pan (Data Infrastructure) <[email protected]>
Date: 2017-06-17T00:16:13Z
SAMZA-1334: fix the pre-conditions for ContainerAllocator to work properly.
Make sure JobModel is generated w/o LocalityManager if host-affinity is disabled
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
