[
https://issues.apache.org/jira/browse/DRILL-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184970#comment-16184970
]
ASF GitHub Bot commented on DRILL-5811:
---------------------------------------
GitHub user ilooner opened a pull request:
https://github.com/apache/drill/pull/965
DRILL-5811 reduced repeated log messages further.
This reduces the number of messages printed for blocks that are on nodes on
which there is no drillbit running. Now the number of messages printed is equal
to the number of nodes on which there are blocks that don't have drillbits. For
example if there are 6 data nodes and only 2 of those nodes have drill bits,
then exactly 4 messages will be printed. This time around I have tested this on
my own physical cluster.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ilooner/drill DRILL-5811
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/965.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #965
----
commit 872b330199c177e8b7ab847412a1187322547135
Author: Timothy Farkas <[email protected]>
Date: 2017-09-28T19:56:18Z
DRILL-5811 reduced repeated log messages further.
----
> 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
> Assignee: Timothy Farkas
> 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)
