Jason Tedor de43565abc Do not log full bootstrap checks exception ...

By default, when an exception causes the JVM to terminate, the stack
trace is printed. In the case of failing bootstrap checks, this stack
trace is useless to the user, and might even distract them from seeing
that the bootstrap checks failed for reasons under their control. With
this commit, we cause the stack trace for a failing bootstrap check to
be truncated.

We also modify some methods to not declare that they throw the top level
checked exception type Exception, but instead explicitly declare the
exceptions that they throw. These exceptions are caught and wrapped in a
BootstrapException so that we can percolate only two exception types out
of Bootstrap#init as checked exception, BootstrapException and
NodeValidationException.

Relates #19989

2016-09-08 10:56:11 -04:00

..

fixtures

in the plugin: guard against HADOOP_HOME in environment on any platform.

2015-12-21 02:21:53 -05:00

framework

Do not log full bootstrap checks exception

2016-09-08 10:56:11 -04:00

logger-usage

Add empty test to ESLoggerUsageTests

2016-08-31 04:41:07 -04:00

build.gradle

Add authentication to reindex-from-remote

2016-07-27 14:17:41 -04:00