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)
