Return-Path: X-Original-To: apmail-samza-commits-archive@minotaur.apache.org Delivered-To: apmail-samza-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F3C9A197AE for ; Tue, 1 Mar 2016 23:59:22 +0000 (UTC) Received: (qmail 3139 invoked by uid 500); 1 Mar 2016 23:59:22 -0000 Delivered-To: apmail-samza-commits-archive@samza.apache.org Received: (qmail 3109 invoked by uid 500); 1 Mar 2016 23:59:22 -0000 Mailing-List: contact commits-help@samza.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@samza.apache.org Delivered-To: mailing list commits@samza.apache.org Received: (qmail 3100 invoked by uid 99); 1 Mar 2016 23:59:22 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Mar 2016 23:59:22 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E6BDDC39C5 for ; Tue, 1 Mar 2016 23:59:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.021 X-Spam-Level: X-Spam-Status: No, score=-4.021 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 7ws8KaDiGnuM for ; Tue, 1 Mar 2016 23:59:19 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 5EBD95F54E for ; Tue, 1 Mar 2016 23:59:19 +0000 (UTC) Received: (qmail 2607 invoked by uid 99); 1 Mar 2016 23:59:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Mar 2016 23:59:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1E6932C1F55 for ; Tue, 1 Mar 2016 23:59:18 +0000 (UTC) Date: Tue, 1 Mar 2016 23:59:18 +0000 (UTC) From: "Jake Maes (JIRA)" To: commits@samza.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (SAMZA-883) Improve logging for container handling and kafka refresh scenarios MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jake Maes created SAMZA-883: ------------------------------- Summary: Improve logging for container handling and kafka refresh scenarios Key: SAMZA-883 URL: https://issues.apache.org/jira/browse/SAMZA-883 Project: Samza Issue Type: Improvement Reporter: Jake Maes Assignee: Jake Maes We need to improve logging in 2 areas: Container handling: 1. There was a log message that printed the ContainerModel in Samza 9 that is missing in Samza 10. It's useful because it prints the mappings. e.g. 2016-02-25 09:34:24 SamzaAppMasterTaskManager [INFO] Claimed SSP taskNames ContainerModel [containerId=0, tasks={Partition 0=TaskModel [taskName=Partition 0, systemStreamPartitions=[SystemStreamPartition [kafka-input, UnifiedImpressionEvent, 0]], changeLogPartition=Partition [partition=10]]}] for container ID 0 2. Samza 9 also printed info logs when a new container was allocated by the RM. These logs are mostly there in Samza 10 but they're debug level. They're not overly verbose, so lets move them to info. Kafka refresh scenarios: The logs are currently unclear as to what code path is causing abdication in the broker proxy and the content of the topic metadata when we refresh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)