You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Chen Chun (JIRA)" <ji...@apache.org> on 2013/07/30 09:59:49 UTC
[jira] [Commented] (AMBARI-2757) ambari-log4j shouldn't affect the
normal work of JobTracker or Hive
[ https://issues.apache.org/jira/browse/AMBARI-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723534#comment-13723534 ]
Chen Chun commented on AMBARI-2757:
-----------------------------------
I notice that the initialization of DB connection is already moved to the persist method in AMBARI-2427. So there is no chance that it will affect the start of jobTracker when job history db is unavailable.
But if Ambari's job history db is down while jobTracker is running, the LoggingEvent queue may take lots of memory. So I limit the LoggingEvent queue's capacity and change events.add to events.offer to avoid throwing an exception when LoggingEvent queue is full. See TestJobHistoryAppender.
> ambari-log4j shouldn't affect the normal work of JobTracker or Hive
> -------------------------------------------------------------------
>
> Key: AMBARI-2757
> URL: https://issues.apache.org/jira/browse/AMBARI-2757
> Project: Ambari
> Issue Type: Improvement
> Affects Versions: 1.3.1, 1.2.6
> Reporter: Billie Rinaldi
> Attachments: AMBARI-2757.patch
>
>
> If Ambari's job history db is unavailable, it shouldn't affect the running of the JobTracker.
--
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