Affects Version/s: None
Fix Version/s: None
We currently use memory mapped files to buffer data as it's being sorted in an ORDER BY (see MappedByteBufferQueue). The following types of exceptions have been seen to occur:
Andrew Purtell has read that memory mapped files are not cleaned up after very well in Java:
"Map failed" means the JVM ran out of virtual address space. If you search around stack overflow for suggestions on what to do when your app (in this case Phoenix) encounters this issue when using mapped buffers, the answers tend toward manually cleaning up the mapped buffers or explicitly triggering a full GC. See http://stackoverflow.com/questions/8553158/prevent-outofmemory-when-using-java-nio-mappedbytebuffer for example. There are apparently long standing JVM/JRE problems with reclamation of mapped buffers. I think we may want to explore in Phoenix a different way to achieve what the current code is doing.
Instead of using memory mapped files, we could use heap memory, or perhaps there are other mechanisms too.