Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.1.0
-
None
-
None
Description
In FLUME-1273, I thought we may not be handling exceptions coming out of configure() in Configurable components very well. In actuality, the behavior is arguably quite sane. But we should indicate what the implications are in an error message printed to the Flume log, and ideally make the call depth between throw and catch a little less deep, for maintainability / clarity's sake.
The error message in the log could look something like:
ERROR: Exception thrown while attempting to configure component "<foo>". Flume agent will not be started. Exception follows.
... stack trace ...