Comment 11 for bug 1646945

Revision history for this message
Soumil Kulkarni (soumilk) wrote :

For upgrade from 3.0.3 to 3.1 a work around to avoid this issue is:

Edit line number 102 in "/etc/cassandra/cassandra-env.sh" to the following.

if [ "$JVM_VERSION" \< "1.8" ] && [ "$JVM_PATCH_VERSION" -lt "25" ] ; then

(add the '-lt' tag to JVM_PATCH_VERSION instead of the one that is currently there)
-------

After this restart cassandra and things should work for you.