You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by lh...@apache.org on 2020/11/22 01:02:58 UTC

[samza] branch master updated (f2b10e0 -> 4ad502f)

This is an automated email from the ASF dual-hosted git repository.

lhaiesp pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/samza.git.


    from f2b10e0  Merge pull request #1444 from sborya/KEYS
     add 6665098  SAMZA-2601: avoid infinite loop when resource not allocated with host affinity disabled
     add a58125b  update log messages based on feedback
     new 4ad502f  SAMZA-2601: avoid infinite loop when resource not allocated with host affinity disabled (#1441)

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../samza/clustermanager/ContainerAllocator.java   |  9 +++-
 .../MockContainerAllocatorWithoutHostAffinity.java | 41 +++++++++++++++++
 .../TestContainerAllocatorWithoutHostAffinity.java | 53 ++++++++++++++++++++++
 3 files changed, 102 insertions(+), 1 deletion(-)


[samza] 01/01: SAMZA-2601: avoid infinite loop when resource not allocated with host affinity disabled (#1441)

Posted by lh...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

lhaiesp pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/samza.git

commit 4ad502f67470c74c98be0c8f9a884a05ade28483
Merge: f2b10e0 a58125b
Author: Hai Lu <ha...@linkedin.com>
AuthorDate: Sat Nov 21 17:02:50 2020 -0800

    SAMZA-2601: avoid infinite loop when resource not allocated with host affinity disabled (#1441)
    
    Problem: If YARN does not immediately allocate resources for a container and host affinity is disabled for the job, then the container allocator will spam the logs with messages about the request, even if the request is considered expired. This is because the allocator loops over the pending requests to check if they have been allocated, but there is no delay between loop iterations, so it might just keep checking the same pending request over and over as fast as possible. A metric is [...]
    
    Changes: Avoid infinite loop by breaking the loop if host affinity is disabled
    
    Tests: new unit test
    
    API changes: N/A
    
    Usage instructions: N/A
    
    Upgrade instructions: None

 .../samza/clustermanager/ContainerAllocator.java   |  9 +++-
 .../MockContainerAllocatorWithoutHostAffinity.java | 41 +++++++++++++++++
 .../TestContainerAllocatorWithoutHostAffinity.java | 53 ++++++++++++++++++++++
 3 files changed, 102 insertions(+), 1 deletion(-)