Need to prevent GC for lifetime of M/R job
Open
improvement
- Dominant language
- Java
- Stars
- 200
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Description
Work done on #8 made the Fluo GC iter collect based on what Transactions are currently active. When using this Fluo input format all mappers use the same timestamp for reading data, and therefore all read from the same snapshot. Currently nothing is done to ensure data is not GCed for this snapshot.
Contributor guide
Assessment
This issue has not been assessed yet.