[
https://issues.apache.org/jira/browse/CASSANDRA-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244479#comment-13244479
]
Vijay edited comment on CASSANDRA-3997 at 4/2/12 7:20 PM:
----------------------------------------------------------
Segfaults happen in multiple places (opening a file, accessing malloc, while
calling free, and in a lot of unrelated cases)...
Unless we open JDK source code and figure out how it is structured it is hard
to say when exactly it can fails (Let me know if you want to take a look at the
hs_err*.log).
In the bright side at least we can isolate this by calling via JNI, and we dont
see the issue by loading JEMalloc via LD_LIBRARY_PATH. In v2 I removed the
synchronization, i have also attached it here (Plz note the yaml setting is not
included just to hide it for now). Thanks!
Note: "jemalloc 2.2.5" release works fine and so as the git/dev branch.
was (Author: vijay2...@yahoo.com):
Segfaults happen in multiple places (opening a file, accessing malloc,
while calling free, and in a lot of unrelated cases)...
Unless we open JDK source code and figure out how it is structured it is hard
to say when exactly it can fails (Let me know if you want to take a look at the
hs_err*.log).
In the bright side at least we can isolate this by calling via JNI. In v2 I
removed the synchronization, i have also attached it here (Plz note the yaml
setting is not included just to hide it for now). Thanks!
Note: "jemalloc 2.2.5" release works fine and so as the git/dev branch.
> Make SerializingCache Memory Pluggable
> --------------------------------------
>
> Key: CASSANDRA-3997
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3997
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Labels: cache
> Fix For: 1.2
>
> Attachments: 0001-CASSANDRA-3997-v2.patch, 0001-CASSANDRA-3997.patch,
> jna.zip
>
>
> Serializing cache uses native malloc and free by making FM pluggable, users
> will have a choice of gcc malloc, TCMalloc or JEMalloc as needed.
> Initial tests shows less fragmentation in JEMalloc but the only issue with it
> is that (both TCMalloc and JEMalloc) are kind of single threaded (at-least
> they crash in my test otherwise).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
