[jira] [Resolved] (SAMZA-846) Refactor logging in ContainerAllocator and LocalityManager that is flooding the AM log

["Navina Ramesh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SAMZA-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Navina Ramesh resolved SAMZA-846.
---------------------------------
    Resolution: Fixed

> Refactor logging in ContainerAllocator and LocalityManager that is flooding the AM log
> --------------------------------------------------------------------------------------
>
>                 Key: SAMZA-846
>                 URL: https://issues.apache.org/jira/browse/SAMZA-846
>             Project: Samza
>          Issue Type: Bug
>    Affects Versions: 0.10.0
>            Reporter: Navina Ramesh
>            Assignee: Navina Ramesh
>            Priority: Minor
>             Fix For: 0.10.1
>
>         Attachments: SAMZA-846-0.patch
>
>
> 2015-12-17 19:30:31 LocalityManager [INFO] Read locality for container 4: {jmx-url=service:jmx:rmi://localhost:XYZ/jndi/rmi://localhost:XYZ/jmxrmi, host=foo.bar.com, jmx-tunneling-url=service:jmx:rmi://foo.bar.com:XYZ/jndi/rmi://foo.bar.com:XYZ/jmxrmi}
> The above log line gets printed each time the JobModel is refreshed and it prints one line per Coordinator Message of type set-container-host-assignment. This is excessive and floods the log.
> "Requests Queue is empty. Should clear up state."
> The above log line is internal to the ContainerAllocator thread. "state" refers to the internal container request state and not the state store. It is misleading and should not be printed at INFO level.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)