From yarn-issues-return-169547-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Wed Jul 3 09:11:03 2019 Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by minotaur.apache.org (Postfix) with SMTP id 175E71908A for ; Wed, 3 Jul 2019 09:11:03 +0000 (UTC) Received: (qmail 61636 invoked by uid 500); 3 Jul 2019 09:11:02 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 61599 invoked by uid 500); 3 Jul 2019 09:11:02 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 61491 invoked by uid 99); 3 Jul 2019 09:11:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jul 2019 09:11:02 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DA42AE2E82 for ; Wed, 3 Jul 2019 09:11:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 62A3A261E8 for ; Wed, 3 Jul 2019 09:11:00 +0000 (UTC) Date: Wed, 3 Jul 2019 09:11:00 +0000 (UTC) From: "Adam Antal (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-9629) Support configurable MIN_LOG_ROLLING_INTERVAL MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-9629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Antal updated YARN-9629: ----------------------------- Attachment: YARN-9629.006.patch > Support configurable MIN_LOG_ROLLING_INTERVAL > --------------------------------------------- > > Key: YARN-9629 > URL: https://issues.apache.org/jira/browse/YARN-9629 > Project: Hadoop YARN > Issue Type: Improvement > Components: log-aggregation, nodemanager, yarn > Affects Versions: 3.2.0 > Reporter: Adam Antal > Assignee: Adam Antal > Priority: Minor > Attachments: YARN-9629.001.patch, YARN-9629.002.patch, YARN-9629.003.patch, YARN-9629.004.patch, YARN-9629.005.patch, YARN-9629.006.patch > > > One of the log-aggregation parameter, the minimum valid value for {{yarn.nodemanager.log-aggregation.roll-monitoring-interval-seconds}} is MIN_LOG_ROLLING_INTERVAL - it has been hardcoded since its addition in YARN-2583. > It has been empirically set as 1 hour, as lower values would too frequently put the NodeManagers under pressure. For bigger clusters that is indeed a valid limitation, but for smaller clusters it makes sense and a valid customer usecase to use lower values, even like not so lower 30 mins. At this point this can only be achieved by setting {{yarn.nodemanager.log-aggregation.debug-enabled}}, which I believe should be kept as debug purposes. > I'm suggesting to make this min configurable, although a warning should be logged in the NodeManager startup when this value is lower than 1 hour. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org