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

Mrfetcher ignores failed tasks #249

Merged
merged 8 commits into from
May 30, 2017

Conversation

shankar37
Copy link
Contributor

This changes fixes a couple of things

  1. We have been ignoring Failed Tasks in calculation of resource usage. This handles that.
  2. For failed jobs, the Exception heuristic is supposed to give the stacktrace. That wasn't working currently. this changes fixes that.

I still need to test this change with the FS fetcher and potentially add a couple of unittests.

shankar added 7 commits April 14, 2017 18:39
…or uptime is allocated resources and task time is used resources
…w executor uptime is allocated resources and task time is used resources"

This reverts commit b6cbbe4.
…are counted against the resource usage. Also, fixes the exception stack trace not showing for failed jobs
@@ -235,52 +235,53 @@ public MapReduceApplicationData fetchData(AnalyticJob job) throws IOException {
jobData.setFinishTime(jobInfo.getFinishTime());

String state = jobInfo.getJobStatus();
if (state.equals("SUCCEEDED")) {

if( state.equals("SUCCEEDED")) {
Copy link
Contributor

@akshayrai akshayrai May 24, 2017

Choose a reason for hiding this comment

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

Formatting! if-else

<td>{{yarnappheuristicresultdetail.name}}</td>
<td>{{yarnappheuristicresultdetail.value}}</td>
</tr>
{{#if (not-empty yarnappheuristicresultdetail.details) }}
Copy link
Contributor

Choose a reason for hiding this comment

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

In case of a failed job, the heuristic details (name, value and details) are as follows:
Error, Stacktrace, <actual_stacktrace>

It would be good to check if yarnappheuristicresultdetail.name equals "Error" rather than checking if details is non-empty. In the future if we plan to include details for other heuristics then this can break.

@shankar37
Copy link
Contributor Author

@akshayrai Fixed your comments. Take a look and merge if it looks good.

@akshayrai akshayrai merged commit cdf680b into linkedin:master May 30, 2017
skakker pushed a commit to skakker/dr-elephant that referenced this pull request Dec 14, 2017
* We have been ignoring Failed Tasks in calculation of resource usage. This handles that.
* Fixes Exception heuristic which was supposed to give the stacktrace.
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.

2 participants