Daniel Barclay (Drill) created DRILL-3686:
---------------------------------------------
Summary: no-ZooKeeper logging: Curator messages not in main file,
no "trying ZooKeeper" from Drill
Key: DRILL-3686
URL: https://issues.apache.org/jira/browse/DRILL-3686
Project: Apache Drill
Issue Type: Bug
Reporter: Daniel Barclay (Drill)
When Drill is started when ZooKeeper is not running, the logging could be
clearer.
The log messages from Curator (e.g., "ERROR org.apache.curator.ConnectionState
- Connection timed out for connection string (localhost:2181) and timeout
(5000) / elapsed (5568)") don't go to Drill's normal/main log file
.../drillbit.log; instead they go to .../Drillbit.out.
(They'd be easier to notice and find if they were in the main log file where
most of the rest of Drill's logging output is.)
Additionally, at least at the default logging level (for drillbit.sh), nothing
in the main log says that Drill's about to try to connect to ZooKeeper.
(Seeing a "connecting to ZooKeeper" message without a following "connected to
ZooKeeper" message) in the main log would help point the reader to the
secondary log, even if we can't/don't get the Curator log output into the main
log file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
