Database Reference
In-Depth Information
INFO 13:23:22,691 Completed flushing /var/lib/cassandra/data/system/
LocationInfo-e-1-Data.db
INFO 13:23:22,701 Starting up server gossip
INFO 13:23:22,750 Binding thrift service to localhost/127.0.0.1:9160
INFO 13:23:22,752 Using TFramedTransport with a max frame size of 15728640 bytes.
INFO 13:23:22,753 Listening for thrift clients...
INFO 13:23:22,792 mx4j successfuly loaded
HttpAdaptor version 3.0.2 started on port 8081
NOTE
Using the
-f
switch tells Cassandra to stay in the foreground instead of running as a background process,
so that all of the server logs will print to standard out and you can see them in your terminal window,
which is useful for testing.
Congratulations! Now your Cassandra server should be up and running with a new single node
cluster called Test Cluster listening on port 9160.
NOTE
The committers work hard to ensure that data is readable from one minor dot release to the next and
from one major version to the next. The commit log, however, needs to be completely cleared out from
version to version (even minor versions).
If you have any previous versions of Cassandra installed, you may want to clear out the data directories
for now, just to get up and running. If you've messed up your Cassandra installation and want to get
started cleanly again, you can delete the folders in /var/lib/cassandraand /var/log/cassandra.
Running the Command-Line Client Interface
Now that you have a Cassandra installation up and running, let's give it a quick try to make
sure everything is set up properly. On Linux, running the command-line interface just works. On
Windows, you might have to do a little additional work.
On Windows, navigate to the Cassandra home directory and open a new terminal in which to
run our client process:
>bin\cassandra-cli
It's possible that on Windows you will see an error like this when starting the client:
