[
https://issues.apache.org/jira/browse/RATIS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Kumar Singh updated RATIS-767:
------------------------------------
Attachment: RATIS-767.002.patch
> DirectByteBuffers leaked by BufferedWriteChannel in SegmentRaftLog
> ------------------------------------------------------------------
>
> Key: RATIS-767
> URL: https://issues.apache.org/jira/browse/RATIS-767
> Project: Ratis
> Issue Type: Bug
> Components: server
> Reporter: Rajesh Balamohan
> Assignee: Mukul Kumar Singh
> Priority: Major
> Attachments: RATIS-767.001.patch, RATIS-767.002.patch, Screenshot
> 2019-10-25 at 12.20.05 PM.png
>
>
> As noticed by Rajesh, Ratis is leaking DirectByteBuffers in
> BufferedWriteChannel.
> As has been shared in multiple articles on the internet, it is best to
> allocate pool of direct byte buffers and use them from the pool. Please refer
> : https://www.javamex.com/tutorials/io/nio_buffer_direct.shtml
> This jira introduces a BufferPool to avoid memory leaks
> !Screenshot 2019-10-25 at 12.20.05 PM.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
