https://github.com/voldemort/voldemort
Revision 8bfd18280465b5127a1e6508e2bb33237659d600 authored by Arunachalam Thirupathi on 22 January 2015, 19:56:41 UTC, committed by Arunachalam Thirupathi on 22 January 2015, 19:56:41 UTC
If you truncate a read-only store and send read operations get/getall
for one of the existent keys it crashes the JVM with SegFault. Some of
the data is cached in java collections and it tries to access the memory
mapped file which has been closed by the truncate. This causes the JVM
to crash. Now the java collections are cleared and the code tries to
handle this gracefully.  But this is not an ideal code more of a
workaround.

Fixed spewing of log messages to the standard output, as they are
already captured in the log4j loggers.

Added unit test for the read after truncate scenario.
1 parent 8e54d87
History
Tip revision: 8bfd18280465b5127a1e6508e2bb33237659d600 authored by Arunachalam Thirupathi on 22 January 2015, 19:56:41 UTC
Read after truncate crashes the JVM
Tip revision: 8bfd182
File Mode Size
.settings
bin
clients
config
contrib
docs
example
gradle
private-lib
public-lib
src
test
voldemort-contrib
.gitignore -rw-r--r-- 242 bytes
CONTRIBUTORS -rw-r--r-- 659 bytes
LICENSE -rw-r--r-- 11.1 KB
NOTES -rw-r--r-- 2.5 KB
NOTICE -rw-r--r-- 8.1 KB
README.md -rw-r--r-- 4.4 KB
build.gradle -rw-r--r-- 19.5 KB
build.xml -rw-r--r-- 22.1 KB
gradle.properties -rw-r--r-- 1.2 KB
gradlew -rwxr-xr-x 5.0 KB
gradlew.bat -rw-r--r-- 2.3 KB
release_notes.txt -rw-r--r-- 38.8 KB
settings.gradle -rw-r--r-- 149 bytes
tomcat-tasks.properties -rw-r--r-- 420 bytes
web.xml -rw-r--r-- 1.1 KB

README.md

back to top