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

More detailed error logging on segment activities #1568

Merged
merged 2 commits into from
Jul 28, 2015

Conversation

drcrallen
Copy link
Contributor

No description provided.

@nishantmonu51
Copy link
Member

+1

@drcrallen
Copy link
Contributor Author

Java 8 + zk atomicity seems keeps breaking, trying for a better travis CI run

@drcrallen drcrallen closed this Jul 27, 2015
@drcrallen drcrallen reopened this Jul 27, 2015
@@ -63,7 +63,7 @@ public void kill(DataSegment segment) throws SegmentLoadingException
}
}
catch (ServiceException e) {
throw new SegmentLoadingException(e, "Couldn't kill segment[%s]", segment.getIdentifier());
throw new SegmentLoadingException(e, "Couldn't kill segment[%s]: [%s]", segment.getIdentifier(), e);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"e" is already set as the exception "cause", why do we need to put e.toString() in the message as well or did you want to put e.getMessage() ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

E as cause only captures stack trace. E as parameters has a lot of info in its toString

himanshug added a commit that referenced this pull request Jul 28, 2015
More detailed error logging on segment activities
@himanshug himanshug merged commit cc50217 into apache:master Jul 28, 2015
@drcrallen drcrallen deleted the detailedSegmentLoadingErrors branch July 28, 2015 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants