linkedin / linkedin/dr-elephant
cluster have keytab and i configura elephant.conf keytab but no data
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 839
- PR merge metrics
- No merged PRs in 30d
Description
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Fetching jobs for which baseline metrics need to be computed
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.BaselineComputeUtil : Baseline computation complete
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Updating execution status
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Fetching the executions which are in progress
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Number of executions which are in progress: 0
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Fetching the list of executions completed since last iteration
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.AzkabanJobCompleteDetector : Number of executions completed since last iteration: 0
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.JobCompleteDetector : Finished updating execution status
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Computing and updating fitness for completed executions
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Fetching completed executions whose fitness are yet to be computed
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : #completed executions whose metrics are not computed: 0
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Number of completed execution fetched for fitness computation: 0
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.FitnessComputeUtil : Execution metrics updated
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Checking which jobs need new parameter suggestion
10-11-2018 18:47:53 ERROR [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : No auto-tuning enabled jobs found
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Number of job(s) which need new parameter suggestion: 0
10-11-2018 18:47:53 INFO [Auto Tuner Thread] com.linkedin.drelephant.tuning.PSOParamGenerator : Updating new parameter suggestion in database
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 with the elephant.conf keytab settings and the logged execution path through BaselineComputeUtil, JobCompleteDetector, and PSOParamGenerator. Reproduce the cluster configuration and determine why no job data or auto-tuning jobs are found; done means the cause and an observable correction are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100