Transit analysts want MapReduce tasks to run close to the AVL block replicas they read. What benefit does data locality primarily provide?
Select an answer to reveal the explanation.
Short Explanation
Hauling every raw crate across town just to open it is wasteful. Data locality keeps processing near the blocks so the network is not flooded with raw AVL bytes. It is a performance rationale, not a promise of magic millisecond SLAs or OLTP conversion.
Full Explanation
Data locality schedules compute near the DataNodes that hold the needed blocks, cutting network shuffle of raw input. Replication and metadata remain necessary; locality does not remove them. Locality also does not turn Hadoop into an OLTP system or guarantee fixed sub-millisecond latency.