-
Improvement
-
Resolution: Done
-
High
-
None
Currently we create a FileChannel for each JournalSegment's writer and then a separate channel every time we open a reader.
This is needed as long as these are touching FileChannel's position, but once we address that, we can open the file exactly once and share it as needed. The result of doing so is faster reader allocation as well as lower file descriptor usage.
This will need some figuring out due to lifecycle, of these objects, but at the day, the channel should be allocated (and owned) by JournalSegment.
- blocks
-
CONTROLLER-2099 Specialize JournalSegment to specified StorageLevel
- In Progress
-
CONTROLLER-2098 Refactor Journal{Reader,Writer} class hierarchy
- Resolved
- is blocked by
-
CONTROLLER-2094 Do not use FileChannel.position() in FileChannelJournalSegmentReader
- Resolved
-
CONTROLLER-2095 Do not use FileChannel.position() in FileChannelJournalSegmentWriter
- Resolved