[DRILL-3686] no-ZooKeeper logging: Curator messages not in main file, no "trying ZooKeeper" from Drill

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Future
• Assignee: Sorabh Hamirwasia
• Reporter: Daniel Barclay
• Created: 21/Aug/15 20:30
• Updated: 14/Sep/16 21:58

Description

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.