linkedin / linkedin/dr-elephant

Question about large spark application's being throttled

Open
#661 0 comments 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'm kinda new to dr elephant and when I was deploying and testing it on my machines, I found large spark application logs (large than 100MB by default) will be ignored and won't show up in the UI due to the throttle behavior. There might be something I missed, but based on the code, does it mean dr elephant will skip all spark applications whose size is larger than `eventLogSizeLimitMb` (by default 100MB)? Is this how `dataCollection.throttle()` expected to behave? If my understanding is wrong, can someone tell me how the throttle works for large spark applications? If my understanding is right, is there any remarkable bottleneck on dr elephant for large spark applications? I think it's easy for a spark application log to go beyond several GB, and how dr elephant's gonna solve it? Thanks in advance for any helps and suggestions!

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 by tracing dataCollection.throttle() and the eventLogSizeLimitMb configuration. Confirm whether oversized Spark event logs are skipped, identify any existing tests or documentation for that path, and define the expected behavior for multi-GB logs before proposing work.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spark
Domain
observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.