linkedin / linkedin/dr-elephant

Issue with Spark job java.lang.NullPointerException at com.linkedin.drelephant.analysis.AnalyticJob.getAnalysis(AnalyticJob.java:303)

Open
#315 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.4k
Forks
839
PR merge metrics
No merged PRs in 30d

Description

Hi,
I am getting null pointer exception without below line but commented in the code; any reason ?

// This was added for AnalyticTest. Commenting this out to fix a bug. Also disabling AnalyticJobTest.
detail.yarnAppHeuristicResultDetails = new ArrayList();

detail.yarnAppHeuristicResultDetails.add(heuristicDetail);

01-06-2018 22:58:07 ERROR [dr-el-executor-thread-2] com.linkedin.drelephant.ElephantRunner : java.lang.NullPointerException
at com.linkedin.drelephant.analysis.AnalyticJob.getAnalysis(AnalyticJob.java:303)
at com.linkedin.drelephant.ElephantRunner$ExecutorJob.run(ElephantRunner.java:177)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with AnalyticJob.getAnalysis in AnalyticJob.java at line 303 and inspect the initialization of detail.yarnAppHeuristicResultDetails before the failing add call. Review the AnalyticTest and AnalyticJobTest references in the issue, then reproduce the Spark job failure and confirm the null-pointer error is resolved without regressing those tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spark
Domain
observability-sre
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.