Small-file problem: Too many tiny files (KB–MB) cause metadata explosion (S3/HDFS list operations), slow scans, and many small tasks. **Root causes**: High parallelism (many partitions), over-partitioning by high-cardinality key, streaming append with small batches. **Why it...
This hard-level Spark/Big Data question appears frequently in data engineering interviews at companies like Daniel Wellington, Incedo. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (partition, spark, window) will help you answer variations of this question confidently.
This is a senior-level question that tests architectural thinking. Lead with the high-level design, then drill into specifics. Discuss trade-offs explicitly - there is rarely one correct answer. Show awareness of scale, fault tolerance, and operational complexity.
Small-file problem: Too many tiny files (KB–MB) cause metadata explosion (S3/HDFS list operations), slow scans, and many small tasks. Root causes: High parallelism (many partitions), over-partitioning by high-cardinality key, streaming append with small batches. Why it hurts: S3 list costs $0.005/1000 requests; 1M files = $5 just for listing. Query engines (Athena, Presto) open each file; latency grows with file count. Solutions: (1) Coalesce/repartition before write to reduce output partitions. (2) Delta/Parquet auto-compaction (OPTIMIZE). (3) Target file size 128MB–1GB (match block size). (4) Batch streaming writes (e.g., maxFilesPerTrigger) to amortize. Scalability: Compaction itself costs compute; schedule during low-traffic windows. Cost implication: 10K small files vs. 100 optimal files can 10x query cost. Best practice: Monitor output file size distribution; set coalesce targets in CI; use Delta OPTIMIZE ZORDER for hot columns.
This answer is partially locked
Unlock the full expert answer with code examples and trade-offs
Practice real interviews with AI feedback, track progress, and get interview-ready faster.
Pro starts at $24/mo - cancel anytime
Get the most asked SQL questions with expert answers. Instant download.
No spam. Unsubscribe anytime.
Paste your answer and get instant AI feedback with a FAANG-level improved version.
Analyze My Answer — FreeAccording to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 2 companies. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.