steveloughran commented on pull request #3015: URL: https://github.com/apache/hadoop/pull/3015#issuecomment-842281065
+1 One aspect of the Exit code design was that returning != 0 doesn't mean print a stack trace at info. So the exit() calls must only log the message at info, full stack at debug for the curious. halt() is a different story. Looking at the hadoop code there's nowhere where halt is called that it isn't some kind of emergency, often where exit() raised an exception. Which means the stack is important. Given it's logging the stack at info, what about cutting the DEBUG logging? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
