LOCAL_QUORUM without a replica in current data center

Hi, How does LOCAL_QUORUM read/write behave when the data center on which query is executed does not have a replica of the keyspace? Does it result in an error or can it be configured to do LOCAL_QUORUM on the "nearest" data center (as depicted by the dynamic snitch) which has the replicas ? We

cannot login cassandra

Dear All, After creating table “mykeysapce. cffex_l23 “, some data are insert into the table, then the connection is closed and quit; And then reconnection Cassandra, error is thrown. The following errors are recorded in the system.log file. ERROR [SSTableBatchOpen:1] 2014-08-15 17:08:22,912 Cass

Re: Internode encryption

> Hi, > > Is it possible to enable internode encryption without downtime? That is, > by enabling it incrementally one node at a time. [1] doesn't mention > anything about that. > > > [1] http://wiki.apache.org/cassandra/InternodeEncryption > > > Thanks, > Jens > — > Sent from Mailbox I've not d

Internode encryption

Hi, Is it possible to enable internode encryption without downtime? That is, by enabling it incrementally one node at a time. [1] doesn't mention anything about that. [1] http://wiki.apache.org/cassandra/InternodeEncryption Thanks, Jens — Sent from Mailbox

Re: Strange select result when using date grater than query

I am running csql on same machine as my cassandra server. I am observing really strange behavior if I do this query all 3 rows show up. SELECT asset_id,event_time,sensor_type, temperature,humidity from temp_humidity_data ALLOW FILTERING; asset_id | event_time | sensor_type | t

Re: cassandra-stress with clustering columns?

FWIW I tried just removing indices from my table and rerunning my write load test and I got about 2x the performance. I'm still interested, however, in seeing whether I can replicate my table layout in cassandra-stress, just so that I can normalize my results. Should the presence of clustering co

Suggestion for improving cassandra performance

I have table with 128244 entries in it. I am running one cassandra node on AWS EC2 x.large instance. Cassandra is the only daemon running on this machine. Its SSD storage. Its taking cassandra python driver running on another machine 7 seconds to retrieve that data. This is pretty small table wit

cassandra-stress with clustering columns?

Hi all, Is there a way to use the cassandra-stress tool with clustering columns? I am trying to figure out whether an application that I'm running on is slow because of my application logic, C* data model, or underlying C* setup (e.g., I need more nodes or to tune some parameters). My applicatio

Re: Compaction before Decommission and Bootstrapping

If you are migrating all nodes, you might want to consider creating a new data center, bringing up all the new nodes (bootstrap) in that new data center, and then decommissioning all the nodes in the old data center. That way, the existing nodes remain fully operational during the process, and

Re: Compaction before Decommission and Bootstrapping

In a few words: Bootstrap one node at once Wait for bootstrap to complete Next node More details: datastax.com/docs (C* 2.0) Before decommissioning: nodetool cleanup Don't forget to do repairs (one node at a time) - this should be a regular admin task -- Sent from my iPhone > Am 17.08.2014

Re: Strange select result when using date grater than query

I should have asked where your coordinator node is located. Check its time zone, relative to GMT. cqlsh is simply formatting the time stamp for your local display. That is separate from the actual query execution on the server coordinator node. cqlsh is merely a "client", not the "server". And

Re: Strange select result when using date grater than query

I am in PST ( Oakland ). I am storing the timestamp in UTC in my insert code, and I see that cqlsh converts the timestamp to local timezone? i.e. if I set TZ=EST cqlsh shows me time stamps in EST like this for the same data set. SELECT asset_id,event_time,sensor_type, temperature,humidity from t

Compaction before Decommission and Bootstrapping

Is there some unwritten wisdom with regards to the use 'nodetool compact' before bootstrapping new nodes and decommissioning old ones? TL;DR: I've been spending the last few days trying to move a cluster on DigitalOcean 2GB machines to 4GB machines (same provider). To do so I wanted to create the

Re: Strange select result when using date grater than query

Are you more than 7 time zones behind GMT? If so, that would make 03:33 your query less than 03:33-0700 Your query is using the default time zone, which will be the time zone configured for the coordinator node executing the query. IOW, where are you? -- Jack Krupansky -Original Message

Strange select result when using date grater than query

Hello, I am fairly new to cassandra so this might be naieve question: I have table that currently has following entries: SELECT asset_id,event_time,sensor_type, temperature,humidity from temp_humidity_data where asset_id='2'; asset_id | event_time | sensor_type | temperature | hu