[jira] [Updated] (SAMZA-883) Improve logging for container handling and kafka refresh scenarios

["Jake Maes (JIRA)" <ji...@apache.org>]

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

Jake Maes updated SAMZA-883:
----------------------------
    Attachment: SAMZA-883.patch

Attaching patch. 

RB: https://reviews.apache.org/r/44241/

> Improve logging for container handling and kafka refresh scenarios
> ------------------------------------------------------------------
>
>                 Key: SAMZA-883
>                 URL: https://issues.apache.org/jira/browse/SAMZA-883
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Jake Maes
>            Assignee: Jake Maes
>         Attachments: SAMZA-883.patch
>
>
> We need to improve logging in 2 areas:
> Container handling:
> 1. There was a log message that printed the ContainerModel in Samza 9 that is missing in Samza 10. It's useful because it prints the mappings. e.g.
> 2016-02-25 09:34:24 SamzaAppMasterTaskManager [INFO] Claimed SSP taskNames ContainerModel [containerId=0, tasks={Partition 0=TaskModel [taskName=Partition 0, systemStreamPartitions=[SystemStreamPartition [kafka-input, UnifiedImpressionEvent, 0]], changeLogPartition=Partition [partition=10]]}] for container ID 0
> 2. Samza 9 also printed info logs when a new container was allocated by the RM. These logs are mostly there in Samza 10 but they're debug level. They're not overly verbose, so lets move them to info.
> Kafka refresh scenarios:
> The logs are currently unclear as to what code path is causing abdication in the broker proxy and the content of the topic metadata when we refresh. 



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