Hi all,
I am facing the above issue in Cassandra 1.1.0, it will add 134.2MB
commitlog file in every restart, but it never delete it. We can't control
the commitlog dir size even
by explicitly setting commitlog_total_space_in_mb in cassandra.yaml.
I set commitlog_total_space_in_mb as 512 in cassan
have you flushed the node using NODETOOL after renaming the cluster?
Is your /etc/hosts correct? Does it have an entry for beta.jokefire.com
What if you replace beta.jokefire.com with the ip address, can you connect?
Can you telnet to beta.jokefire.com port 9160?
Look in the system log and see if you have a log entry like
INFO [main] CassandraDaemon.jav
Hello,
I'm using:
[cqlsh 2.0.0 | Cassandra 1.0.10 | CQL spec 2.0.0 | Thrift protocol 19.20.0]
I have a column family with a key that is a blob so I query it like this:
SELECT FIRST 10 1..1344385804 FROM WHERE KEY =
'436170616369747943616c63756c61746f727c33';
Is there any way to avoid the
Hi,
Can somebody tell me if is there some benefit in use SSD Disks
for commitlog?
THanks!
I think I'm having a major brain fart here, I am just not getting something.
I have the following CF declared in CQL -3
create columnfamily testCQL5( ac_event_id int, ac_c text,
ac_mtcreation bigint, ac_action text , ac_id text, PRIMARY KEY (ac_c,
ac_mtcreation));
I can do this:
cqlsh:op2> selec
Thanks! That got the value inserted properly
[default@system] set LocationInfo[utf8('L')][utf8('Test
Cluster')]=utf8('Jokefire Cluster');
Value inserted.
Elapsed time: 5 msec(s).
But if I go into the yaml file and set the cluster name
# The name of the cluster. This is mainly used to prevent m
[default@system] set LocationInfo[utf8('L')][utf8('Test
Cluster')]=utf8('Jokeire Cluster');
Value inserted.
You are missing set
Amit
On Aug 7, 2012, at 5:36 PM, Tim Dunphy wrote:
> hello,
>
> I'd like to change my cluster name from the default 'Test Cluster' to
> something a little more
hello,
I'd like to change my cluster name from the default 'Test Cluster' to
something a little more reflective of the site name. I am using cassandra
1.1.3.
So I tried following the instructions from the wiki, intending to modify
the cassandra.yaml file after I performed these steps:
[default@
Hi
I have upgrade the production cassandra cluster to 1.0.11 version.
But still one node sending hints to a other node in cluster every 10 mins.
All the nodes in cluster are up and running and well balanced. Log says:
2012-08-08 08:56:54,380 INFO [HintedHandOffManager] Started hinted handoff
Perform these steps on each node:
Start the Cassandra-cli connected to your node.
Run the following:
1. use system;
2. set LocationInfo[utf8('L')][utf8('ClusterName')]=utf8('Brisk
Cluster');
3. exit;
4. Run nodetool flush on this node.
5. Update the cassandra.yaml file for the c
Yes.
On Thu, Aug 2, 2012 at 5:33 AM, Radim Kolar wrote:
>
>> 1) I assume that I have to call the loadNewSSTables() on each node?
>
> this is same as "nodetool refresh?"
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http
Hi,
Thank you very much for your useful info.
I have one more doubt here.
If i create one more column family based on my query instead of going with
secondary index,
Will it affect the write performance?
Since i need to duplicate the data in the second column family as well
while writing data, Wi
13 matches
Mail list logo