Re: java.io.IOException: Failed during snapshot creation

my Cassandra folder's owner,group are cassandra On Tue, May 26, 2015 at 2:20 AM, Brice Argenson wrote: > I also have the same kind of exceptions once. It was caused by a bad > configuration of the Cassandra data folder permissions (process running as > user Cassandra with root as owner of the fo

Re: Leveled Compaction Strategy with a really intensive delete workload

Hi Stefano, I did a quick test, it looks almost instant if you do alter but remember, in my test machine, there are no loaded data yet and switching from stcs to lcs. cqlsh:jw_schema1> CREATE TABLE DogTypes ( block_id uuid, species text, alias text, population varint, PRIMARY KEY (block_id) ) WIT

Re: Leveled Compaction Strategy with a really intensive delete workload

Ok, I am reading a bit more about compaction subproperties here ( http://docs.datastax.com/en/cql/3.1/cql/cql_reference/compactSubprop.html) and it seems that tombstone_threshold and unchecked_tombstone_compaction might come handy. Does anybody know if changing any of these values (via ALTER) is p

Re: java.io.IOException: Failed during snapshot creation

I also have the same kind of exceptions once. It was caused by a bad configuration of the Cassandra data folder permissions (process running as user Cassandra with root as owner of the folder). It was then preventing any snapshot creations during a repair. On Mon, May 25, 2015 at 3:43 PM Yuki Mori

Re: java.io.IOException: Failed during snapshot creation

Hi, it can be timimg out waiting for snapshot to complete. See https://issues.apache.org/jira/browse/CASSANDRA-8696 for workaround. On Mon, May 25, 2015 at 10:44 AM, Mark Reddy wrote: > Can you check your logs for any other other error message around the time of > the repair? Something to look fo

Re: java.io.IOException: Failed during snapshot creation

Can you check your logs for any other other error message around the time of the repair? Something to look for would be "Error occurred during snapshot phase". Regards, Mark On 25 May 2015 at 14:56, Sachin PK wrote: > Hey I'm new to Cassandra ,I have 4 node cluster with each node 16GB VPS, > i

Re: read-only DC (or oneway replication)

Have separate connection config for readers and writers. Let the writers connect only to the SAFE DC. readers can read from wherever they want. Use replication to replicate from SAFE to UNSAFE dc. From the server side, why not use the firewall to open ports for only the apps that you want

java.io.IOException: Failed during snapshot creation

Hey I'm new to Cassandra ,I have 4 node cluster with each node 16GB VPS, initially I had one seed node, I added one of the existing nodes as seed nodes , restarted nodes one by one after that one of my node went down . I ran nodetool repair on it when I checked the log i could find some errors ER

Re: Leveled Compaction Strategy with a really intensive delete workload

Hi all, Thanks for your answers! Yes, I agree that a delete intensive workload is not something Cassandra is designed for. Unfortunately this is to cope with some unexpected data transformations that I hope are a temporary thing. We chose LCS strategy because of really wide rows which were spa

RE: Drop/Create table with same CF Name

Totally agree with this. From: Ken Hancock [mailto:ken.hanc...@schange.com] Sent: 22 May 2015 17:10 To: user@cassandra.apache.org Subject: Re: Drop/Create table with same CF Name This issue really needs to be strongly highlighted in the documentation. Imagine someone noticing similarities betwe

Concurrent schema creation/change strategy

I have a lot of clients that will try to create the same schema (a keyspace with multiple tables) concurrently during application startup. The idea is that the first time the application starts, the clients will create the schema needed to run (create if not exists, etc...) From what I’ve read,

Re: Leveled Compaction Strategy with a really intensive delete workload

, due to a really intensive delete workloads, the SSTable is promoted to t.. Is cassandra design for *delete* workloads? doubt so. Perhaps looking at some other alternative like ttl? jason On Mon, May 25, 2015 at 10:12 AM, Manoj Khangaonkar wrote: > Hi, > > For a delete intensive workl

Re: read-only DC (or oneway replication)

Could you use Cassandra security roles so that only your application on the untrusted site had write permissions? http://docs.datastax.com/en/cassandra/2.1/cassandra/security/secure_intro.html On Mon, 25 May 2015 at 7:34 pm Andreas Baumhof wrote: > Hi, > > > > We operate several Cassandra cluste

read-only DC (or oneway replication)

Hi, We operate several Cassandra clusters in various geographies. We are in the process of extending this cluster into an "unfriendly" geography where we may be forced not to trust anything. I obviously don't want to "pollute" my main DC's with potential fraudulent writes, so I'm looking for a