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

Be less verbose logging ClusterInfoUpdateJob failures #5222

Conversation

dakrone
Copy link
Member

@dakrone dakrone commented Feb 21, 2014

No description provided.

@spinscale
Copy link
Contributor

This patch results in no chance (not even with another loglevel) to access the stack trace anymore. Is that ok for this case?

@dakrone
Copy link
Member Author

dakrone commented Feb 26, 2014

@spinscale good idea, I decided to change this to log the full exception if trace logging is enabled, at the trace level.

dakrone added a commit that referenced this pull request Mar 27, 2014
@dakrone dakrone closed this in 9ef5136 Mar 27, 2014
@kimchy
Copy link
Member

kimchy commented Apr 4, 2014

can we re-open this? I think its cleaner to warn log the full exception, bug if the exception is a cluster block exception (for example, during startup), simply trace log it.

@dakrone
Copy link
Member Author

dakrone commented Apr 4, 2014

@kimchy sure, I'll make that change.

@dakrone dakrone deleted the tone-down-cluster-update-info-job-logging branch April 21, 2014 23:02
@clintongormley clintongormley added >enhancement :Core/Infra/Logging Log management and logging utilities labels Jun 8, 2015
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.

None yet

5 participants