**Why control matters**: Mappers = input splits; too many = overhead; too few = underutilization. **Levers**: (1) Split size: `mapreduce.input.fileinputformat.split.maxsize`—larger = fewer mappers. (2) Small files: `CombineFileInputFormat` merges small files into splits. (3) Compression: Splittable formats (LZO, Snappy) enable parallelism; non-splittable (gzip) = one mapper per file. **Scalability trade-offs**: 100–200MB splits = good balance; small files = mapper explosion....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like JP Morgan. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.