Re: Is replication possible with already existing data?

Hi Michael. Please find below the contents of cassandra.yaml for CAS11 (the files on the rest of the three nodes are also exactly the same, except the "initial_token" and "listen_address" fields) :: CAS11 :: cluster_name: 'InstaMsg Cluster' num_tokens: 256 in

Re: Automatic pagination does not get all results

It’s possible that it could be different depending on your consistency level (on write and on read). It’s also possible it’s a bug, but you didn’t give us much information – here are some questions to help us help you: What version? What results are you seeing? What’s the “right” result? Wha

Re: Is replication possible with already existing data?

On 10/22/2015 10:14 PM, Ajay Garg wrote: However, CAS11 refuses to come up now. Following is the error in /var/log/cassandra/system.log :: ERROR [main] 2015-10-23 03:07:34,242 CassandraDaemon.java:391 - Fatal configuration error o

Re: Is replication possible with already existing data?

Hi Carlos. I setup a following setup :: CAS11 and CAS12 in DC1 CAS21 and CAS22 in DC2 a) Brought all the 4 up, replication worked perfect !!! b) Thereafter, downed CAS11 via "sudo service cassandra stop". Replication continued to work fine on CAS12, CAS21 and CAS22. c) Thereafter, upped CAS11

[ANNOUNCE] YCSB 0.4.0 Release

On behalf of the development community, I am pleased to announce the release of YCSB 0.4.0. Highlights: * Default measurement changed from histogram to hdrhistogram. * Users who want previous behavior can set the 'measurementtype' property to 'histogram'. * Reported 95th and 99th perce

Automatic pagination does not get all results

Hello, Has anyone had a problem with automatic pagination returning different results everytime (this is for a table with ~180,000 rows)? I'm going through each page and inserting the results into an array and each time I go through all the pages, the resultant array has a different size. This ha

Re: Anything special about upgrading from 2.0 to 2.1

On Thu, Oct 22, 2015 at 12:35 PM, Robert Wille wrote: > I’m on 2.0.16 and want to upgrade to the latest 2.1.x. I’ve seen some > comments about issues with counters not migrating properly. I have a lot of > counters. Any concerns there? Do I need to run nodetool upgradesstables? > Any other gotcha

Anything special about upgrading from 2.0 to 2.1

I’m on 2.0.16 and want to upgrade to the latest 2.1.x. I’ve seen some comments about issues with counters not migrating properly. I have a lot of counters. Any concerns there? Do I need to run nodetool upgradesstables? Any other gotchas? Thanks Robert

Data Streamed successfully but not queryable

Apologies for the long post but it's a complicated story... I am running Cassandra in 3 datacenters 1,2 & 3. DCs 1 and 2 are working fine but I am having trouble selecting any data at all in DC 3. I've stripped DC3 down from 4 nodes to a single brand new node to make debugging logs/traces etc e

Re: cassandra bootstrapping

> I keep on seeing that there should be a 2 minute delay when bootstrapping a cluster, and > I have few questions round that. > > For starters, is there any reasoning why this is 2min and not less or more? > Is this valid mostly for bootstraping an empty cluster ring or for > restarting an existin

cassandra bootstrapping

Hey everyone, I keep on seeing that there should be a 2 minute delay when bootstrapping a cluster, and I have few questions round that. For starters, is there any reasoning why this is 2min and not less or more? Is this valid mostly for bootstraping an empty cluster ring or for restarting an exi

Re: C* Table Changed and Data Migration with new primary key

Use Spark to distribute the job of copying data all over the cluster and help accelerating the migration. The Spark connector does auto paging in the background with the Java Driver Le 22 oct. 2015 11:03, "qihuang.zheng" a écrit : > I tried using java driver with *auto paging query: setFetchSize*

Re: C* Table Changed and Data Migration with new primary key

Consider the new 3.0 Materialized Views feature - you keep the existing table and create three MVs, each with a different a primary key. Cassandra will then populate the new MVs from the existing base table data. See: https://issues.apache.org/jira/browse/CASSANDRA-6477 -- Jack Krupansky On Wed,

Re: C* Table Changed and Data Migration with new primary key

I tried using java driver with auto paging query: setFetchSize instead of token function. as Cass has this feature already. ref from here:http://www.datastax.com/dev/blog/client-side-improvements-in-cassandra-2-0 But I tried in test envrionment with only 1million data read then insert 3 tables

Re: Object Mapping VS Direct Queries

Cons: - depending on the object mapper and the features, you may (or may not) have some slight overhead at runtime - the CQL query may be "hidden" from the developer, though some object mappers like Achilles has an option to display DML statements in the logs Pros: - make your life easier by remo