Cassandra 2.1: Snapshot data changing while transferring

Hi there, i am sometimes running in very strange errors while backing up snapshots from a cassandra cluster. Cassandra version: 2.1.11 What i basically do: 1. nodetool snapshot 2. tar all snapshot folders into one file 3. transfer them to another server What happens is that tar just sometimes

Re: [Marketing Mail] Cassandra 2.1: Snapshot data changing while transferring

Hi Paul, I guess this might come from the incremental repairs... The repair time is stored in the sstable (RepairedAt timestamp metadata). Cheers, Reynald On 31/05/2016 11:03, Paul Dunkler wrote: Hi there, i am sometimes running in very strange errors while backing up snapshots from a cassan

Re: [Marketing Mail] Cassandra 2.1: Snapshot data changing while transferring

Hi there, > I guess this might come from the incremental repairs... > The repair time is stored in the sstable (RepairedAt timestamp metadata). ok, that sounds interesting. Could that also happen to incremental backup files as well? I had another case where incremental backup files were totally

Re: [Marketing Mail] Cassandra 2.1: Snapshot data changing while transferring

And - as an addition: Shoudln't that be documented that even snapshot files can change? > I guess this might come from the incremental repairs... >> The repair time is stored in the sstable (RepairedAt timestamp metadata). > > ok, that sounds interesting. > Could that also happen to incremental

a question to Stratio's Cassandra Lucene Index

Hi, All, We are considering to support more flexible searching on data in the Cassandra DB (used in our product). For example, full-text search and query data based on different columns. After some investigating, I found https://github.com/Stratio/cassandra-lucene-index/blob/branch-2.1.8/doc/sr

Re: a question to Stratio's Cassandra Lucene Index

Hi, Stratio’s Lucene index plugin for C* is currently used in production by several Stratio customers in banking, insurance, security, media, etc. The main usage is for analytics, with and without Spark. It is also used in near-real-time scenario

RE: Cassandra data modeling for a social network

Hello, > First, Is this data modeling correct for follow base (follower, following actions) social network? For social network, I advise you to see Graph Databases, over Cassandra Example : https://academy.datastax.com/resources/getting-started-graph-databases De : Mohammad Kermani [mail

Re: Cassandra data modeling for a social network

Or use graphframes (Spark) over cassandra to store separately a graph of users and followers and next a table of tweet. You will be able to join data between those 2 structures using spark. 2016-05-31 14:27 GMT+02:00 : > Hello, > > >* First, Is this data modeling correct for follow base (fo

Re: C* working with Open JDK but not Oracle JDK

On Fri, May 27, 2016 at 4:30 PM, Drew Davis wrote: > I am running C* 2.1.4 on an Ubuntu vagrant VM. When I use OpenJDK 8, C* > works fine. However using Oracle JDK 8, I get the errors listed below. I > have read that it is not recommended to use Open JDK so I would like to be > able to use the Ora

Does sstableloader still use gossip?

Hi, in the docs it still says that the sstableloader still uses gossip ( https://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsBulkloader_t.html http://docs.datastax.com/en/cassandra/3.x/cassandra/tools/toolsBulkloader.html ) but this blog ( http://www.datastax.com/dev/blog/using-the-ca

Re: [Marketing Mail] Cassandra 2.1: Snapshot data changing while transferring

Hi Paul, what is the value of the snapshot_before_compaction property in your cassandra.yaml? Say if another snapshot is being taken (because compaction kicked in and snapshot_before_compaction property is set to TRUE) and at this moment you're tarring the snapshot folders.. Maybe can take a

RE: Per node limit for Disk Space

Eric is right on. Let me share my experience. I have found that dense nodes over 4 TB are a pain to manage (for rebuilds, repair, compaction, etc.) with size-tiered compaction and basically a single table schema. However, 1 TB nodes that yield only about 500 GB of usable space can create rings