I'm guessing things here without checking, but some issues may be:
* pretty sure JNA mlockall() to lock the cassandra memory from swapping is not
available https://issues.apache.org/jira/browse/CASSANDRA-1214
* Creating hard links for the snapshots will be different, not sure exactly how
differ
I'm wondering what the consensus is for running a Cassandra cluster on top of
Windows boxes? We are currently running a small 5 node cluster on top of
CentOS without problems, so I have no desire to move. But we are a windows
shop, and I have an IT department that is scared of Linux since they
On Mon, Mar 15, 2010 at 11:41 PM, Jesus Ibanez wrote:
> To run Cassandra on Windows, after executing bin\cassandra without problems,
> we need to insert the line if NOT DEFINED CASSANDRA_HOME set
> CASSANDRA_HOME=%CD% into the cassandra-cli.bat file before we execute it.
> That line is missing in
Im sorry Jonathan. I didn't know it was the cli, I thought the problem was
with cassandra.bat becouse it doesn't show the output: Starting up server...
Instead, it shows: Starting up server gossip...
But the problem was in the cassandra-cli.bat.
The nice new is that know we know that we have to m
Your time on IRC would have been a lot more productive if you had
mentioned that bin\cassandra was working fine and you were stuck on
the cli. :(
On Mon, Mar 15, 2010 at 11:41 PM, Jesus Ibanez wrote:
> To run Cassandra on Windows, after executing bin\cassandra without problems,
> we need to inser
To run Cassandra on Windows, after executing bin\cassandra without problems,
we need to insert the line if NOT DEFINED CASSANDRA_HOME set
CASSANDRA_HOME=%CD% into the cassandra-cli.bat file before we execute it.
That line is missing in cassandra-cli.bat, so add it and Cassandra will
execute perfect
