[ 
https://issues.apache.org/jira/browse/SAMZA-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740652#comment-13740652
 ] 

Chris Riccomini commented on SAMZA-14:
--------------------------------------

I'll number, but I want to move to RB anyway -- still waiting on the INFRA 
ticket.

logging stacktrace: I'm thinking of it from the steady-state perspective. You 
have a job happily running along. It times out to the broker periodically, or 
spins when there's a network partition or whatever. The case you're describing 
sounds like a case where you should turn debug on. Maybe we can add "Turn debug 
on for more details" to the error message, or something. I'm just really 
sensitive to filling the logs with meaningless junk in the "happy path", which 
is what happens if you do ", e)". We had it that way in 0.6, and the logs are 
really messy. I don't want to be in a situation where we're telling people to 
ignore stack traces because it's not an error.

Logging: YARN does not handle rolling over STDOUT. Indeed, there does not seem 
to be a good/easy way to do this on Linux. Some solutions require piping STDOUT 
through a tool that does the rolling. I have not seen a way to do this easily. 
I don't think M/R handles it either. The correct approach is to use a logging 
system that rolls the logs properly.

Config: we need to open a "make config suck less" ticket, and get on it. It's 
just a bit painful right now. It doesn't help that we (..or I..) keep renaming 
config parameters on master either.
                
> Fix misc bugs in QA jobs
> ------------------------
>
>                 Key: SAMZA-14
>                 URL: https://issues.apache.org/jira/browse/SAMZA-14
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jay Kreps
>            Assignee: Jay Kreps
>         Attachments: SAMZA-14-v1.patch
>
>
> Some bugs that have already been there and some that came with the various 
> package refactorings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to