Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Togglable stacktrace display #5187

Conversation

timorantalaiho
Copy link
Contributor

Make it flaggable with system property whether ES will display
only Throwable message or full stack trace on startup, as
suggested by @imotov in #5103 discussion. Defaults to
displaying stack trace, but it can be suppressed by
-Des.suppress-stack-traces=true .

Closes #5102

@kimchy
Copy link
Member

kimchy commented Mar 27, 2014

you could get this by setting bootstrap level logging to DEBUG, right? @imotov maybe I am missing something?

@imotov
Copy link
Contributor

imotov commented Mar 28, 2014

@kimchy yes you can get it, but only in the log file. When you run it in foreground you only get error message. I guess we could piggy back on the bootstrap:DEBUG setting and use it in foreground as well. So, it would console output and log would be consistent.

@kimchy
Copy link
Member

kimchy commented Mar 28, 2014

@imotov ++, makes sense.

@timorantalaiho
Copy link
Contributor Author

Thankyou for the comments! Is this what we're after, then?

@kimchy
Copy link
Member

kimchy commented Mar 30, 2014

@timorantalaiho something similar, just without changing the default bootstrap category to DEBUG

This makes it a lot easier to debug a problem like

{2.0.0-SNAPSHOT}: Startup Failed ...
- NumberFormatException[For input string: ""]

because now you see from where the error comes from (which might be from
a plugin!).

Whether or not the stacktrace is displayed is controlled by bootstrap
log level setting, so that bootstrap: DEBUG displays the stack trace on
output, like it does on log, as suggested by @imotov
elastic#5187 (comment)
@timorantalaiho
Copy link
Contributor Author

All right, removed it even though I as an ES user would greatly appreciate getting the stack traces of startup by default :)

@javanna javanna self-assigned this Apr 4, 2014
@javanna
Copy link
Member

javanna commented Apr 4, 2014

Merged, thanks @timorantalaiho !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Display full stack trace of exception that occurs on startup
6 participants