[
https://issues.apache.org/jira/browse/SAMZA-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398142#comment-15398142
]
Jake Maes commented on SAMZA-954:
---------------------------------
My original feedback was on RB: https://reviews.apache.org/r/47992/
The new RB is: https://reviews.apache.org/r/50583/
> Improve logging for Samza
> -------------------------
>
> Key: SAMZA-954
> URL: https://issues.apache.org/jira/browse/SAMZA-954
> Project: Samza
> Issue Type: Bug
> Reporter: Jagadish
> Assignee: Jake Maes
> Attachments: SAMZA-954_1.patch
>
>
> Often Samza jobs keep running for days (and in our case months). Often log
> messages generated by the job get rolled over. A lot of information that is
> critical for debugging a job (like the jmx server port, URL, job model for
> the current container, configuration that was passed to the container) is
> often printed when the job starts. However, since logs get rolled over (by
> Yarn/ by sys-administrators) when they exceed a certain size, this
> information is lost.
> This JIRA is to add a separate samza-container-$containerID-startup.log file
> with each container. This will have information useful for debugging the job.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
