cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-11716) cassandra 2.2 fails to start on jdk7u101
Date Thu, 05 May 2016 07:30:13 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sam Tunnicliffe resolved CASSANDRA-11716.
-----------------------------------------
    Resolution: Duplicate

> cassandra 2.2 fails to start on jdk7u101
> ----------------------------------------
>
>                 Key: CASSANDRA-11716
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11716
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: ubuntu 12.04 fully updated
>            Reporter: Tiago Batista
>         Attachments: cassandra-env.patch
>
>
> Today I updated one of my clusters to 2.2.6, and was greeted with the message complaining
about the jdk version:
> {code}
> $ nodetool status
> Cassandra 2.0 and later require Java 7u25 or later.
> {code}
> After digging into it, on cassandra-env.sh, i found that you are comparing the patch
levels as strings, meaning that "101" is before "25":
> {code}
> if [ "$JVM_VERSION" \< "1.8" ] && [ "$JVM_PATCH_VERSION" \< "25" ] ; then
>     echo "Cassandra 2.0 and later require Java 7u25 or later."
>     exit 1;
> fi
> {code}
> I patched this on my system to
> {code}
> if [ "$JVM_VERSION" \< "1.8" ] && [ "$JVM_PATCH_VERSION" -lt "25" ] ; then
>     echo "Cassandra 2.0 and later require Java 7u25 or later."
>     exit 1;
> fi
> {code}
> this seems to work on bash. I can now start cassandra successfully on that cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message