You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Daniel Chen (JIRA)" <ji...@apache.org> on 2019/02/26 02:20:00 UTC
[jira] [Updated] (SAMZA-2108) Check for host affinity config before
resolving preferred host matching
[ https://issues.apache.org/jira/browse/SAMZA-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Chen updated SAMZA-2108:
--------------------------------
Fix Version/s: 1.0.1
> Check for host affinity config before resolving preferred host matching
> -----------------------------------------------------------------------
>
> Key: SAMZA-2108
> URL: https://issues.apache.org/jira/browse/SAMZA-2108
> Project: Samza
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Daniel Chen
> Assignee: Daniel Chen
> Priority: Major
> Fix For: 1.0.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> We are seeing an issue where if host affinity was enabled in the past, there will exist a host mapping in the coordinator stream. The system will read this mapping regardless if host-affinity is enabled on subsequent deploys.
> Need to add a check for that in the ContainerAllocator.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)