Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B514C200CC8 for ; Fri, 9 Jun 2017 03:38:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B3D36160BD5; Fri, 9 Jun 2017 01:38:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 05960160BE5 for ; Fri, 9 Jun 2017 03:38:21 +0200 (CEST) Received: (qmail 47577 invoked by uid 500); 9 Jun 2017 01:38:21 -0000 Mailing-List: contact commits-help@beam.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@beam.apache.org Delivered-To: mailing list commits@beam.apache.org Received: (qmail 47568 invoked by uid 99); 9 Jun 2017 01:38:20 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Jun 2017 01:38:20 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 98B251A024A for ; Fri, 9 Jun 2017 01:38:20 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 6XQpwpcyOmWb for ; Fri, 9 Jun 2017 01:38:19 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2A6515F6C7 for ; Fri, 9 Jun 2017 01:38:19 +0000 (UTC) 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 7C8DAE0363 for ; Fri, 9 Jun 2017 01:38:18 +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 1FD2121B51 for ; Fri, 9 Jun 2017 01:38:18 +0000 (UTC) Date: Fri, 9 Jun 2017 01:38:18 +0000 (UTC) From: "Kenneth Knowles (JIRA)" To: commits@beam.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (BEAM-2326) Verbose INFO logging with stateful DoFns and Dataflow MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 09 Jun 2017 01:38:22 -0000 [ https://issues.apache.org/jira/browse/BEAM-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenneth Knowles resolved BEAM-2326. ----------------------------------- Resolution: Fixed Fix Version/s: 2.0.0 > Verbose INFO logging with stateful DoFns and Dataflow > ------------------------------------------------------ > > Key: BEAM-2326 > URL: https://issues.apache.org/jira/browse/BEAM-2326 > Project: Beam > Issue Type: Bug > Components: runner-dataflow > Affects Versions: 0.6.0 > Reporter: peay > Assignee: Kenneth Knowles > Labels: log > Fix For: 2.0.0 > > > I am seeing a lot of INFO level logging: > {code} > jsonPayload: { > logger: "com.google.cloud.dataflow.worker.runners.worker.BatchModeUngroupingParDoFn" > message: "Processing timers for key {} for stateful DoFn" > } > jsonPayload: { > message: "Processing key KV{one of my keys} for stateful DoFn" > logger: "com.google.cloud.dataflow.worker.runners.worker.BatchModeUngroupingParDoFn" > } > {code} > out of one of my stateful DoFn. There is one such group of logs for each key I process, which leads to a very large amount of logs and possibly to a significant slowdown. > Also, not sure if the {{Processing timers}} log message is missing some string interpolation or if the empty key is on purpose. > At any rate, this seems more like something for {{DEBUG}} than {{INFO}} given the large volume. -- This message was sent by Atlassian JIRA (v6.3.15#6346)