linkedin / linkedin/dr-elephant
tez get job error
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 839
- PR merge metrics
- No merged PRs in 30d
Description
10-30-2018 12:28:33 ERROR [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : Index: 0, Size: 0
10-30-2018 12:28:33 ERROR [dr-el-executor-thread-1] com.linkedin.drelephant.ElephantRunner : java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at com.linkedin.drelephant.tez.fetchers.TezFetcher.fetchData(TezFetcher.java:125)
at com.linkedin.drelephant.tez.fetchers.TezFetcher.fetchData(TezFetcher.java:40)
at com.linkedin.drelephant.analysis.AnalyticJob.getAnalysis(AnalyticJob.java:247)
at com.linkedin.drelephant.ElephantRunner$ExecutorJob.run(ElephantRunner.java:175)
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:748)
37.png
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading com.linkedin.drelephant.tez.fetchers.TezFetcher.fetchData at TezFetcher.java:125 and inspect the Tez job data that produces the empty list shown in the stack trace. Trace the caller in AnalyticJob.java and determine the expected behavior for this case; done means the reported Tez job no longer fails with IndexOutOfBoundsException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- hadoop, java
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100