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 B74DF200D01 for ; Fri, 22 Sep 2017 22:06:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B60A41609E6; Fri, 22 Sep 2017 20:06:04 +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 05CEC1609BE for ; Fri, 22 Sep 2017 22:06:03 +0200 (CEST) Received: (qmail 60700 invoked by uid 500); 22 Sep 2017 20:06:03 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 60690 invoked by uid 99); 22 Sep 2017 20:06:03 -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; Fri, 22 Sep 2017 20:06:03 +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 ACF6CD81B7 for ; Fri, 22 Sep 2017 20:06:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id TKWFEOAky1vh for ; Fri, 22 Sep 2017 20:06:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id F07495F24F for ; Fri, 22 Sep 2017 20:06:01 +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 1B47AE0ECF for ; Fri, 22 Sep 2017 20:06:01 +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 483742422E for ; Fri, 22 Sep 2017 20:06:00 +0000 (UTC) Date: Fri, 22 Sep 2017 20:06:00 +0000 (UTC) From: "Paul Rogers (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DRILL-5811) Large number of "Failure finding Drillbit" messages when using MFS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 22 Sep 2017 20:06:04 -0000 Paul Rogers created DRILL-5811: ---------------------------------- Summary: Large number of "Failure finding Drillbit" messages when using MFS Key: DRILL-5811 URL: https://issues.apache.org/jira/browse/DRILL-5811 Project: Apache Drill Issue Type: Bug Affects Versions: 1.12.0 Reporter: Paul Rogers Priority: Minor A query was run on a single node of a three-node cluster running the MapR file system (MFS.) When planning the query, zillions of messages of the following form appear in the log: {code} 2017-09-21 16:18:19,401 [263bb743-aaf9-eeb1-2006-32d573e03eba:foreman] INFO o.a.d.exec.store.dfs.FileSelection - FileSelection.getStatuses() took 0 ms, numFiles: 1 2017-09-21 16:18:19,408 [263bb743-aaf9-eeb1-2006-32d573e03eba:foreman] DEBUG o.a.d.e.s.schedule.BlockMapBuilder - Failure finding Drillbit running on host qa-node113.qa.lab. Skipping affinity to that host. 2017-09-21 16:18:19,409 [263bb743-aaf9-eeb1-2006-32d573e03eba:foreman] DEBUG o.a.d.e.s.schedule.BlockMapBuilder - FileWork group (maprfs:///drill/testdata/resource-manager/250wide.tbl,0) max bytes 17132639127 2017-09-21 16:18:19,409 [263bb743-aaf9-eeb1-2006-32d573e03eba:foreman] DEBUG o.a.d.e.s.schedule.BlockMapBuilder - Took 1 ms to set endpoint bytes {code} Might we put such messages a TRACE level, leaving an aggregate message at DEBUG level, something like: {code} 123 files to be read using remote reads because of missing Drillbit processes. Enable trace logging for details. {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)