On Sat, Feb 12, 2011 at 2:52 AM, Xiaobo Gu <guxiaobo1...@gmail.com> wrote:
> On Fri, Feb 11, 2011 at 11:54 PM, Sylvain Lebresne <sylv...@datastax.com> > wrote: > > > > > > On Fri, Feb 11, 2011 at 4:27 PM, Xiaobo Gu <guxiaobo1...@gmail.com> > wrote: > >> > >> On Fri, Feb 11, 2011 at 11:21 PM, Roland Gude < > roland.g...@yoochoose.com> > >> wrote: > >> > This is a problem with the start scripts, not with Cassandra itself > (or > >> > any of its configuration) > >> > The shell you are using cannot start the cassandra shell script. > >> > > >> > Try > >> > #bash bin/cassandra -f > >> You are right, but there are other problems, but you help me make a > >> big step, I'll dig dipper tomorrow. > >> > >> -bash-3.00$ /bin/bash bin/cassandra -f > >> Error occurred during initialization of VM > >> Could not reserve enough space for object heap > >> -bash-3.00$ > > > > You apparently don't have enough free memory available for the > > default setting (1G). Uncomment and change the value of > > MAX_HEAP_SIZE in conf/cassandra-env.sh. > > > >> > >> Does the start script automatically choose the 64bit Java virtual > >> machine, I have both 64bit and 32bit jdk installed. > > > > It either use $JAVA_HOME/bin/java if $JAVA_HOME is defined in > > your environment or the value returned by `which java`. > > 32bit and 64bit java binaries are mixed up in one repository, there is > a $JAVA_HOME/bin/java, and there is also a $JAVA_HOME/bin/amd64/java, > I think the first one is 32bit and the second is 64bit, how can I > choose the 64bit one. Look at bin/cassandra. It's a shell script that, in particular set the JAVA variable that is the used binary. A quick (though slightly dirty) way to force the binary would be to hardcode the value in there. Otherwise, if you unset the $JAVA_HOME variable and make sure the 64 bit binary is in your path (but not the 32 bit one, or "after"), that will work too. -- Sylvain > >> > >> > As far as I know, it should work fine. Actually it should work with sh > >> > as well... > >> > > >> > > >> > -----Ursprüngliche Nachricht----- > >> > Von: Xiaobo Gu [mailto:guxiaobo1...@gmail.com] > >> > Gesendet: Freitag, 11. Februar 2011 16:12 > >> > An: user@cassandra.apache.org > >> > Betreff: Re: cassandra solaris x64 support > >> > > >> > On Fri, Feb 11, 2011 at 10:51 PM, Jonathan Ellis <jbel...@gmail.com> > >> > wrote: > >> >> The vast majority run on Linux, but there are a few people running > >> >> Cassandra on Solaris, FreeBSD, and Windows. > >> > But I failed to start the one node test cluster, > >> > # sh bin/cassandra -f > >> > bin/cassandra: syntax error at line 22: `MAX_HEAP_SIZE=$' unexpected > >> > > >> > My environemnt is as follwoing: > >> > # more /etc/release > >> > Solaris 10 10/09 s10x_u8wos_08a X86 > >> > Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. > >> > Use is subject to license terms. > >> > Assembled 16 September 2009 > >> > > >> > # java -fullversion > >> > java full version "1.6.0_23-b05" > >> > # java -version > >> > java version "1.6.0_23" > >> > Java(TM) SE Runtime Environment (build 1.6.0_23-b05) > >> > Java HotSpot(TM) Client VM (build 19.0-b09, mixed mode, sharing) > >> > > >> > I changed initial_token:0 > >> > > >> > > >> >> On Fri, Feb 11, 2011 at 4:40 AM, Xiaobo Gu <guxiaobo1...@gmail.com> > >> >> wrote: > >> >>> Hi, > >> >>> Because I can't access the archives of the mailing list, so my > >> >>> apologies if someone have asked this before. > >> >>> > >> >>> Does any have successfully run Cassandra on Solaris 10 X64 clusters? > >> >>> > >> >>> Regards, > >> >>> > >> >>> Xiaobo Gu > >> >>> > >> >> > >> >> > >> >> > >> >> -- > >> >> Jonathan Ellis > >> >> Project Chair, Apache Cassandra > >> >> co-founder of DataStax, the source for professional Cassandra support > >> >> http://www.datastax.com > >> >> > >> > > >> > > >> > > > > > >
