XCom size limitations and alternatives in Apache Airflow - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does Airflow limit XCom size?

Airflow has a default size limit for XCom data. Why is this limit important?

A To stop tasks from running longer than their timeout

B To prevent the metadata database from growing too large and slowing down the scheduler

C To avoid tasks from failing due to memory overflow in worker nodes

D To ensure XCom data is encrypted automatically

💡 Hint

Think about what happens if too much data is stored in the Airflow metadata database.

Airflow stores XCom data in its metadata database. Large XComs can cause the database to grow quickly, which slows down the scheduler and affects performance.

💻 Command Output

intermediate

What happens when an XCom exceeds the size limit?

Given a task that tries to push an XCom value larger than the default limit, what is the expected behavior?

Apache Airflow

task_instance.xcom_push(key='large_data', value='x' * 5000000)  # 5MB string

A The scheduler crashes due to database overload

B The XCom is silently truncated to the allowed size and task succeeds

C The task succeeds and the full data is stored without error

D The task fails with an AirflowException about XCom size limit

💡 Hint

Consider what Airflow does to protect the metadata database from large data.

When an XCom value exceeds the size limit, Airflow raises an AirflowException to prevent storing too large data.

✅ Best Practice

advanced

Best alternative to large XCom data

If you need to share large data between tasks in Airflow, which approach is best to avoid XCom size limits?

A Store the data in an external storage like S3 or a database and pass the reference via XCom

B Split the data into many small XComs under the size limit

C Compress the data and push it as a single XCom

D Increase the Airflow XCom size limit in the configuration

💡 Hint

Think about scalable and reliable ways to share large data between tasks.

Storing large data externally and passing only a reference in XCom keeps the metadata database small and avoids size limits.

❓ Troubleshoot

advanced

Diagnosing XCom size limit errors

You see a task failing with an error mentioning XCom size limit. What is the most effective first step to fix this?

A Modify the task to store large data externally and push only a reference in XCom

B Restart the Airflow scheduler to clear the error

C Increase the worker memory to handle larger XComs

D Delete old XCom entries from the metadata database manually

💡 Hint

Think about the root cause of the error and how to avoid it.

The error occurs because the task tries to push too large data. Changing the task to store data externally and push a reference fixes the root cause.

🔀 Workflow

expert

Design a workflow to handle large data passing between tasks

You have a DAG where Task A generates a 100MB file and Task B needs to process it. How should you design the data passing to avoid XCom size limits?

A Task A encodes the file content as base64 and pushes it via XCom; Task B decodes it

B Task A splits the file into 10MB chunks and pushes each chunk as separate XComs; Task B reassembles them

C Task A uploads the file to S3 and pushes the S3 path via XCom; Task B downloads from S3 using the path

D Task A pushes the file content directly via XCom; Task B reads it from XCom

💡 Hint

Consider scalability, reliability, and Airflow best practices for large data.

Uploading large files to external storage and passing only the path via XCom is the recommended approach to handle large data efficiently.