Hi Dwight,
I can confirm that issue on my MBP under Mountain Lion.
Can you create a ticker at https://issues.apache.org/jira/browse/CASSANDRA and
include the platform you are running on.
For reference the change was added by
https://issues.apache.org/jira/browse/CASSANDRA-4447
The change is only relevant if you are running on Java 7. As a work around
change the relevant section of cassandra-env.sh to look like
#startswith () [ "${1#$2}" != "$1" ]
if [ "`uname`" = "Linux" ] ; then
# reduce the per-thread stack size to minimize the impact of Thrift
# thread-per-client. (Best practice is for client connections to
# be pooled anyway.) Only do so on Linux where it is known to be
# supported.
#if startswith "$JVM_VERSION" '1.7.'
#then
# JVM_OPTS="$JVM_OPTS -Xss160k"
#else
JVM_OPTS="$JVM_OPTS -Xss128k"
#fi
fi
Cheers
-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 13/08/2012, at 5:16 PM, Dwight Smith <dwight.sm...@genesyslab.com> wrote:
> Installed 1.1.3 on my Linux cluster – the JVM_OPTS were truncated due to a
> script error in Cassandra-env.sh:
>
> Invalid token in the following.
>
> startswith () [ "${1#$2}" != "$1" ]
>
