Re: datacorruption with cassandra 2.1.11

which exact version you saw this? On Wed, May 15, 2019 at 12:03 PM keshava wrote: > I gave a try with changing java version , and it worked. seems to be some > issue with java version of choice. > > On 10-May-2019 14:48, "keshava" wrote: > >> i will try with changing java version. >> w.r.t othe

Re: Multi-DC replication and hinted handoff

Are you using OSS C*? On Fri, Mar 29, 2019 at 1:49 AM Jens Fischer wrote: > Hi, > > I have a Cassandra setup with multiple data centres. The vast majority of > writes are LOCAL_ONE writes to data center DC-A. One node (lets call this > node A1) in DC-A has accumulated large amounts of hint files

Re: Inter-node messaging latency

Inter-node messaging is rewritten using Netty in 4.0. It will be better to test it using that as potential changes will mostly land on top of that. On Mon, Nov 26, 2018 at 7:39 AM Yuji Ito wrote: > Hi, > > I'm investigating LWT performance with C* 3.11.3. > It looks that the performance is bound

Re: Released an ACID-compliant transaction library on top of Cassandra

What License did you use? Can we please use Apache 2.0? On Tue, Oct 16, 2018 at 9:39 AM sankalp kohli wrote: > This is awesome and thanks for working on it. > > On Tue, Oct 16, 2018 at 9:37 AM Ariel Weisberg wrote: > >> Hi, >> >> Yes this does sound great.

Re: Released an ACID-compliant transaction library on top of Cassandra

This is awesome and thanks for working on it. On Tue, Oct 16, 2018 at 9:37 AM Ariel Weisberg wrote: > Hi, > > Yes this does sound great. Does this rely on Cassandra's internal SERIAL > consistency and CAS functionality or is that implemented at a higher level? > > Regards, > Ariel > > On Tue, Oc

Apache Cassandra Blog is now live

Hi, Apache Cassandra Blog is now live. Check out the first blog post. http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html Thanks, Sankalp

Re: storing indexes on ssd

Cassandra does not support this currently. You can create a JIRA and start the conversation On Sat, Feb 10, 2018 at 11:09 PM, Dan Kinder wrote: > Hi, > > We're optimizing Cassandra right now for fairly random reads on a large > dataset. In this dataset, the values are much larger than the keys.

Re: Introducing Cassandra 3.7 LTS

x27;s great to compare notes. > > On Thu, 20 Oct 2016 at 16:19 sankalp kohli wrote: > >> This is awesome. I have send out the patches which we back ported into >> 2.1 on the dev list. >> >> On Wed, Oct 19, 2016 at 4:33 PM, kurt Greaves >> wrote: >> >

Re: Introducing Cassandra 3.7 LTS

This is awesome. I have send out the patches which we back ported into 2.1 on the dev list. On Wed, Oct 19, 2016 at 4:33 PM, kurt Greaves wrote: > > On 19 October 2016 at 21:07, sfesc...@gmail.com > wrote: > >> Wow, thank you for doing this. This sentiment regarding stability seems >> to be wid

Re: Disable reads during node rebuild

This might be useful Nodetool command to disable reads On Wed, May 14, 2014 at 8:31 AM, Paulo Ricardo Motta Gomes < paulo.mo...@chaordicsystems.com> wrote: > That's a nice workaround, will be really helpful in emergency situations > like this

Re: Possibly losing data with corrupted SSTables

You might want to look at this JIRA i filed today CASSANDRA-6696 You are good if you are fine with data reappearing. On Wed, Feb 12, 2014 at 9:20 AM, Francisco Nogueira Calmon Sobral < fsob...@igcorp.com.br> wrote: > Hi, Rahul. > > I've rem

Re: Clarification on how multi-DC replication works

@Mullen, I think your diagram does not answer the question on responses. @Sameer All nodes in DC2 will replay back to the co-ordinator in DC1. So if you have replication of DC1:3,DC2:3. A co-ordinator node will get 6 responses back if it is not in the replica set. Hope that answers your question.

Re: 1.2.15 non-seed nodes never join cluster. JOINING: waiting for schema information to complete

If you don't have a schema, you are probably hitting this https://issues.apache.org/jira/browse/CASSANDRA-6685 On Tue, Feb 11, 2014 at 8:22 AM, John Pyeatt wrote: > I am trying to bring up a 6 node cluster in AWS. 3 seed nodes and 3 > non-seed nodes. One of each in each availability zone with 1.

Re: Question about node tool repair

Can you give the logs of both the machines. Logs will tell why it is taken so long. On a side note, you are using 2500 Cfs. I think you need to redesign this schema. Also 2 node cluster with RF=2, you might want to add a machine if it is prod. On Mon, Jan 20, 2014 at 2:47 PM, Logendran, Dharsan

Re: HintedHandoff Exception and node holding hints to random tokens

is worse > by an order of magnitude. deleteHintsForEndpoint fails with the same error > on any of the affected nodes. > > -Allan > > On January 20, 2014 at 12:24:33 PM, sankalp kohli > (kohlisank...@gmail.com) > wrote: > > Is this happening in one node or all. Di

Re: HintedHandoff Exception and node holding hints to random tokens

Is this happening in one node or all. Did you try to delete the hints via JMX in other nodes? On Mon, Jan 20, 2014 at 12:18 PM, Allan C wrote: > Hi , > > I’m hitting a very odd issue with HintedHandoff on 1 node in my 12 node > cluster running 1.2.13. Somehow it’s holding a large amount of hint

Re: one or more nodes were unavailable.

Also do you have any nodes down...because it is possible to reach write consistency and not do CAS because some machines are down. On Mon, Jan 20, 2014 at 12:16 PM, sankalp kohli wrote: > What consistency level are you using? > > > On Mon, Jan 20, 2014 at 7:16 AM, Vivek Mishra wr

Re: one or more nodes were unavailable.

What consistency level are you using? On Mon, Jan 20, 2014 at 7:16 AM, Vivek Mishra wrote: > Hi, > Trying CAS feature of cassandra 2.x and somehow getting given below error: > > > cqlsh:sample> insert into "User"(user_id,first_name) values( > fe08e810-81e4-11e3-9470-c3aa8ce77cc4,'vivek1') if no

Re: nodetool repair stalled

Hi, Can you attach the logs around repair. Please do that for node which triggered it and nodes involved in repair. I will try to find something useful. Thanks, Sankalp On Wed, Jan 8, 2014 at 10:18 AM, Robert Coli wrote: > On Wed, Jan 8, 2014 at 8:52 AM, Paolo Crosato < > paolo.cros...@tar

Re: Gotchas when creating a lot of tombstones

With Level compaction, you will have some data which could not be reclaimed with gc grace=0 because it has not compacted yet. For this you might want to look at tombstone_threshold On Wed, Jan 8, 2014 at 10:31 AM, Tyler Hobbs wrote: > > On Wed, Jan 1, 2014 at 7:53 AM, Robert Wille wrote: > >>

Re: Recommended amount of free disk space for compaction

Apart from the compaction, you might want to also look at free space required for repairs. This could be problem if you have large rows as repair is not at column level. > On Nov 28, 2013, at 19:21, Robert Wille wrote: > > I’m trying to estimate our disk space requirements and I’m wondering

Re: RangeSliceCommand serialize issue

Have you done any migration? Can you correlate these errors with any activity? On Thu, Oct 10, 2013 at 8:00 AM, Ravikumar Govindarajan < ravikumar.govindara...@gmail.com> wrote: > We have suddenly started receiving RangeSliceCommand serializer errors. > > We are running 1.2.4 version > > This do

Re: Row Mutation Errors while upgrading to Cassandra2.0

"It is quite possible that this is expected, major version upgrades semi-frequently spam logs with non-pathological error messages." The exception is while trying to deserialize the endpoints in the remote DC. Due to this error, the mutation will not be applied to any node in the remote DC. On M

Re: Row Mutation Errors while upgrading to Cassandra2.0

no such issues were noticed (perhaps testing > happened in single DC is the reason for that). > > > > BTW, we are using GossipingPropertyFileSnitch ….so could that be the > reason. > -- > > *Thanks & Regards* > > * > Shashilpi Kr

Re: Row Mutation Errors while upgrading to Cassandra2.0

You are upgrading to 2.0 in Prod? What is the urgency? On Sun, Sep 22, 2013 at 7:02 PM, Shashilpi Krishan < shashilpi.kris...@wizecommerce.com> wrote: > Hi Everyone. > > > > We had a Cassandra cluster (running with v1.0.7) spread across 3 data > centers with each data center having 16 nodes. We

Re: Commit log and data separation on SSD

Having commit log and data directory under one SSD works well. Though it depends a lot on the use case. I would measure the Disk utilization and see whether it can be on one. For most of the cases, it will work fine on one SSD. On Sun, Sep 22, 2013 at 4:02 PM, Shahryar Sedghi wrote: > This my f

Re: Is it possible to control the sstable file size in incremental backup or snapshot

Snapshot just creates a hard link to all your sstables. There is no control on the size. That you can control if you are on level compaction. Dont know about Size tiered. On Fri, Sep 20, 2013 at 6:56 PM, java8964 java8964 wrote: > Hi, > > The current our production is using Cassandra 1.0, and w

Re: NetworkTopologyStrategy Error

Is any of your keyspace still reference this DC? On Thu, Sep 19, 2013 at 3:03 PM, Ashley Martens wrote: > I tried to split my cluster and ran into this error, which I did not see > in the tests I performed. > > ERROR [pool-1-thread-52165] 2013-09-19 21:48:08,262 Cassandra.java (line > 3250) Inte

Re: 1.2 leveled compactions can affect big bunch of writes? how to stop/restart them?

You cannot start level compaction. It will run based on data in each level. On Thu, Sep 19, 2013 at 9:19 AM, Nate McCall wrote: > As opposed to stopping compaction altogether, have you experimented with > turning down compaction_throughput_mb_per_sec (16mb default) and/or > explicitly setting c

Re: TTL and gc_grace_Seconds

You might want to do some stuff in the application layer. If you can deal with deleted deletes in the application layer, you can reduce your gc-grace period. On Wed, Sep 18, 2013 at 7:42 AM, horschi wrote: > Hi Christopher, > > in 2.0 gc_grace should be capped by TTL anyway: see CASSANDRA-4917

Re: How can I switch from multiple disks to a single disk?

I think you can do by moving all the sstables under one drive. I am not sure though. The sstables names should be unique across drives. On Mon, Sep 16, 2013 at 10:14 AM, Juan Manuel Formoso wrote: > Because I ran out of space when shuffling, I was forced to add multiple > disks on my Cassandra n

Re: Read query slows down when a node goes down

ata is quite small, 1.5GB on each node when running nodetool status. Is > there anyway to speed up repairs? (FYI, I haven’t actually seen a repair > finish since it didn’t retrun after 10 mins – I figured I was doing > something wrong). > > ** ** > > *From:* sankalp kohli [ma

Re: Read query slows down when a node goes down

to wait from the time the down > node is started to the point where it’s ready to be used? If so, what’s > that time? If it’s dynamic, how would I know when it’s ready? > > ** ** > > Thanks, > > Parag > > ** ** > > *From:* sankalp kohli [mailto:kohl

Re: Read query slows down when a node goes down

What is your replication factor? DO you have multi-DC deployment? Also are u using v nodes? On Sun, Sep 15, 2013 at 7:54 AM, Parag Patel wrote: > Hi, > > ** ** > > We have a six node cluster running DataStax Community Edition 1.2.9. From > our app, we use the Netflix Astyanax library to re

Re: FileNotFoundException while inserting (1.2.8)

The reason this is happening is that there are two instances of SStablereader object. A restart of Cassandra will fix the issue. On Sep 11, 2013, at 10:23, Robert Coli wrote: > On Wed, Sep 11, 2013 at 10:12 AM, Keith Freeman <8fo...@gmail.com> wrote: >> I had seen that issue before, but it'

Re: heavy insert load overloads CPUs, with MutationStage pending

What have you set these to? # commitlog_sync may be either "periodic" or "batch." # When in batch mode, Cassandra won't ack writes until the commit log # has been fsynced to disk. It will wait up to # commitlog_sync_batch_window_in_ms milliseconds for other writes, before # performing the sync. #

Re: FileNotFoundException while inserting (1.2.8)

Have you dropped and recreated a keyspace with the same name recently? On Tue, Sep 10, 2013 at 8:40 AM, Keith Freeman <8fo...@gmail.com> wrote: > While running a heavy insert load, one of my nodes started throwing this > exception when trying a compaction: > > INFO [CompactionExecutor:23] 2013-

Re: Cassandra 1.2.4 - Unflushed data lost on restart

You should be using replication. Not all machines will power off at the same time. Regarding changing the fsync setting, even if you choose it to be fully sync, there have been many studies which have shown that data was lost on many SSDs even after fsync has returned. So I will fix this problem by

Re: write load while idle?

Storing OpsCenter data on the same cluster you are monitoring might not work well. I had an issue in which Cassandra had issues and OpsCenter wont load. You might want to store this data in some other cluster or create a fake DC and assign OpsCenter data to that fake DC. On Thu, Aug 22, 2013 at 4

Re: Periodical deletes and compaction strategy

The problem is that tombstones will hang in there till GC grace period. You can reduce the GC grace period and then catch lost deletes in the application layer if you know you should not be seeing such an old record. Also in 1.2, they have some setting which enable an sstable to be compacted if it

Re: conflict resolution in range scans

It will compare them using timestamps. You might want to look at RowRepairResolver. On Sun, Aug 25, 2013 at 2:23 PM, Nate McCall wrote: > See that last part on this page: > http://wiki.apache.org/cassandra/ReadRepair > > This doc is dated, but I'm pretty sure it still works this way. > > > On S

Re: Vnodes, adding a node ?

What steps did you follow to add the 3 node? On Wed, Aug 14, 2013 at 12:02 PM, Andrew Cobley wrote: > I have small test cluster of 2 nodes. I ran a stress test on it and with > nodetool status received the following: > > /usr/local/bin/apache-cassandra-2.0.0-rc1/log $ ../bin/nodetool status >

Re: Unable to bootstrap node

existing nodes before worrying > about the new node. > > Cheers > > - > Aaron Morton > Cassandra Consultant > New Zealand > > @aaronmorton > http://www.thelastpickle.com > > On 6/08/2013, at 1:25 PM, sankalp kohli wrote: > > Let me know if thi

Re: Unable to bootstrap node

Let me know if this fixes the problem? On Mon, Aug 5, 2013 at 6:24 PM, sankalp kohli wrote: > So the problem is that when you dropped and recreated the table with the > same name, some how the old CFStore object was not purged. So now there > were two objects which caused same sstable

Re: Unable to bootstrap node

we likely dropped and recreated tables. If we stop the sending node, > what will happen to the bootstrapping node? > > sankalp kohli wrote: > > > Hi, > The problem is that the node sending the stream is hitting this > FileNotFound exception. You need to restart this

Re: Unable to bootstrap node

Hi, The problem is that the node sending the stream is hitting this FileNotFound exception. You need to restart this node and it should fix the problem. Are you seeing lot of FileNotFoundExceptions? Did you do any schema change recently? Sankalp On Mon, Aug 5, 2013 at 5:39 PM, Keith Wright

Re: maximum storage per node

Try putting multiple instances per machine with each instance mapped to its own disk. This might not work with v-nodes On Thu, Jul 25, 2013 at 9:04 AM, Pruner, Anne (Anne) wrote: > I actually wrote my own compactor that deals with this problem. > > ** ** > > Anne > > ** ** > > *From:* c

Re: sstable size change

"Will Cassandra force any newly compacted files to my new setting as compactions are naturally triggered" Yes. Let it compact and increase in size. On Tue, Jul 23, 2013 at 9:38 AM, Robert Coli wrote: > On Tue, Jul 23, 2013 at 6:48 AM, Keith Wright wrote: > >> Can you elaborate on what you mean

Re: sstable size change

You can remove the json file and that will be treated as all sstables are now in L0. Since you have lot of data, the compaction will take a very long time. See the comment below directly from Cassandra code. If you chose to do this, you might want to increase the rate of compaction by usual means.

Re: How to avoid inter-dc read requests

Slice query does not trigger background read repair. Implement Read Repair on Range Queries<https://issues.apache.org/jira/browse/CASSANDRA-967> On Sun, Jul 21, 2013 at 1:40 PM, sankalp kohli wrote: > There can be multiple reasons for that > 1) Background read repairs. > 2) Y

Re: How to avoid inter-dc read requests

There can be multiple reasons for that 1) Background read repairs. 2) Your data is not consistent and leading to read repairs. 3) For writes, irrespective of the consistency used, a single write request will goto other DC 4) You might be running other nodetools commands like repair. read_repair_cha

Re: Safely adding new nodes without losing data

Interesting... I guess you have to add one node at a time and run repair on it. On Sat, Jul 20, 2013 at 7:30 AM, E S wrote: > I am trying to understand the best procedure for adding new nodes. The > one that I see most often online seems to have a hole where there is a low > probability of per

Re: Auto Discovery of Hosts by Clients

With Auto discovery, you can provide the DC you are local to and it will only use hosts from that. On Fri, Jul 19, 2013 at 2:08 PM, Shahab Yunus wrote: > Hello, > > I want my Thrift client(s) (using hector 1.1-3) to randomly connect to any > node in the Cassandra (1.2.4) cluster. > > 1- One way

Re: MailBox Impl

Conter wont be updated when the old data is TTLed. I am not sure whether you can use triggers https://issues.apache.org/jira/browse/CASSANDRA-1311 On Thu, Jul 18, 2013 at 2:30 PM, Kanwar Sangha wrote: > Hi - We are planning on using Cassandra for an IMAP based > implementation. There are some

Re: Corrupted sstable and sstableloader

sstable might be corrupted due to bad disk. In that case, replication does not matter. On Thu, Jul 18, 2013 at 8:52 AM, Jan Kesten wrote: > Hello together, > > today I experienced a problem while loading a snapshot from our cassandra > cluster to test cluster. The cluster has six nodes and I to

Re: How many DCs can you have in a cluster?

More than the DC, I think you will be bound by number of replicas. I dont know how it will work in case of 10-20 replication factor specially for range queries. On Thu, Jul 11, 2013 at 7:14 PM, Blair Zajac wrote: > In this C* Summit 2013 talk titled "A Deep Dive Into How Cassandra > Resolves I

Re: merge sstables

He has around 10G of data so should not be bad. This problem is if you have lot of data. On Thu, Jul 11, 2013 at 2:10 PM, Robert Coli wrote: > On Thu, Jul 11, 2013 at 1:52 PM, sankalp kohli wrote: > >> Scrub will keep the file size same. YOu need to move all sstables to be >>

Re: merge sstables

Scrub will keep the file size same. YOu need to move all sstables to be L0. the way to do this is to remove the json file which has level information. On Thu, Jul 11, 2013 at 11:48 AM, chandra Varahala < hadoopandcassan...@gmail.com> wrote: > yes, but nodetool scrub is not working .. > > > than

Re: Quorum reads and response time

The coordinator node has to merge the results from 2 nodes and the request is done in parallel. I have seen lot of GC pressure with range queries because of tombstones. Can you see logs to see if there is lot of GC going on. Also try to have GC log enabled. On Wed, Jul 10, 2013 at 9:57 AM, Baskar

Re: Leveled Compaction, number of SStables growing.

PM, PARASHAR, BHASKARJYA JAY wrote: > Thanks Sankalp…I will look at these.**** > > ** ** > > *From:* sankalp kohli [mailto:kohlisank...@gmail.com] > *Sent:* Tuesday, July 09, 2013 3:22 PM > *To:* user@cassandra.apache.org > > *Subject:* Re: Leveled Compaction, nu

Re: Leveled Compaction, number of SStables growing.

Do you have lot of sstables in L0? Since you moved from size tiered compaction with lot of data, it will take time for it to compact. You might want to increase the compaction settings to speed it up. On Tue, Jul 9, 2013 at 12:33 PM, PARASHAR, BHASKARJYA JAY wrote: > Thanks Jake. Guess we will

Re: Node tokens / data move

Hi Aaron, Can he not specify all 256 tokens in the YAML of the new cluster and then copy sstables? I know it is a bit ugly but should work. Sankalp On Tue, Jul 9, 2013 at 3:19 AM, Baskar Duraikannu < baskar.duraikannu...@gmail.com> wrote: > Thanks Aaron > > On 7/9/13, aaron morton

Re: Trying to write when at cassandra capacity

I dont know what exactly will happen. These are the things which might happen 1) Commit log on disk gets recycled so I am assuming it might keep working. 2) SStable wont be able to create new files so it will see an IO exception. On Mon, Jul 8, 2013 at 5:58 PM, Faraaz Sareshwala wrote: > What

Re: Migrating data from 2 node cluster to a 3 node cluster

spaces behind is OK if you are not using vnodes. > > Cheers > >- > Aaron Morton > Freelance Cassandra Consultant > New Zealand > > @aaronmorton > http://www.thelastpickle.com > > On 9/07/2013, at 10:03 AM, sankalp kohli wrote: > > "I

Re: Migrating data from 2 node cluster to a 3 node cluster

"If RF=N or RF>N, you can just copy all SStables to all nodes, watching out for name collision." This might work for user created keyspaces but might not work for system keyspace On Mon, Jul 8, 2013 at 2:07 PM, Robert Coli wrote: > On Fri, Jul 5, 2013 at 7:54 PM, srmore wrote: > >> RF of old

Re: CassandraDaemon - recent unsafe memory access operation in compiled Java code

have u dropped the JNA jar? Looks like the mmap is failing. On Fri, Jul 5, 2013 at 8:15 AM, Glyn Davies wrote: > > > Hi, > > Just starting to experiment with Cassandra, and have hit an early snag. > > I'm using 1.2.6 on Ubuntu AWS m1.xlarge instances with the Datastax > Community package and

Re: column sort order and reversed sort performance question

One of the reasons of using reverse order is to skip the tombstones while doing a range query. Here is an example. * Lets say we want to read all the data which is between 10 minutes old upto 60 minute old. If the data is stored from old to new in an sstable, then we have to go over all the tombst

Re: Added nodes to cluster, authentication stopped working

patch cassandra and remove the code which checks auth :) On Wed, Jul 3, 2013 at 6:55 AM, Carlos Rolo wrote: > Hi all, > > I have a Cassandra Cluster running and we recently duplicated the cluster. > > After following all the steps, the cassandra clients started failing with > the following mes

Re: columns disappearing intermittently

Since you are doing QUORAM, looks like the column is not found in 2 machines. Did you switch to vnodes? Try to see which machines are responding when you get the column and when not. Might be able to identity the problem On Wed, Jul 3, 2013 at 4:56 AM, Eric Stevens wrote: > I wonder if one part

Re: Streaming performance with 1.2.6

streamed from the >> node in their own AZ/rack which led to the serial sstable streaming. Is >> this the correct behavior for the snitch? Is there an option to stream from >> multiple replicas across the az/rack configuration? >> >> Mike >> >> >> On Tue, J

Re: Streaming performance with 1.2.6

This was a problem pre vnodes. I had several JIRA for that but some of them were voted down saying the performance will improve with vnodes. The main problem is that it streams one sstable at a time and not in parallel. Jira 4784 can speed up the bootstrap performance. You can also do a zero copy

Re: schema management

You can generate schema through the code. That is also one option. On Mon, Jul 1, 2013 at 4:10 PM, Franc Carter wrote: > > Hi, > > I've been giving some thought to the way we deploy schemas and am looking > for something better than out current approach, which is to use > cassandra-cli scripts.

Re: High-read latency for non-existing rows with LCS and 1.2.5

Try doing request tracing. http://www.datastax.com/dev/blog/tracing-in-cassandra-1-2 On Thu, Jun 27, 2013 at 2:40 PM, Bao Le wrote: > Hi, > > We are using Leveled Compaction with Cassandra 1.2.5. Our sstable size > is 100M. On each node, > we have anywhere from 700+ to 800+ sstables (for al

Re: what happen if coordinator node fails during write

Read this http://www.datastax.com/dev/blog/atomic-batches-in-cassandra-1-2 On Tue, Jun 25, 2013 at 8:45 PM, Andrey Ilinykh wrote: > It depends on cassandra version. As far as I know in 1.2 coordinator logs > request before it updates replicas. If it fails it will replay log on > startup. > In 1

Re: Cassandra as storage for cache data

Apart from what Jeremy said, you can try these 1) Use replication = 1. It is cache data and you dont need persistence. 2) Try playing with memtable size. 3) Use netflix client library as it will reduce one hop. It will chose the node with data as the co ordinator. 4) Work on your schema. You might

Re: Cassandra terminates with OutOfMemory (OOM) error

l data stored in > the entire Cassandra cluster is less than 55 MB. > > Mohammed > > On Jun 21, 2013, at 7:30 PM, "sankalp kohli" > wrote: > > Looks like you are putting lot of pressure on the heap by doing a slice > query on a large row. > Do you have lo

Re: CAS and long lived locks

Also CAS is in 2.0 which is not production ready so I am not sure how you will use it. On Mon, Jun 24, 2013 at 4:35 PM, sankalp kohli wrote: > Assuming that database migration is a one time and rare operation, why > don't you try to grab a lock for a short time. If you are able

Re: CAS and long lived locks

Assuming that database migration is a one time and rare operation, why don't you try to grab a lock for a short time. If you are able to grab it, then you can renew it for a longer time. This will make sure that in case of collision, all contenders wont be locked out for long time. You can use Netf

Re: Cassandra terminates with OutOfMemory (OOM) error

Looks like you are putting lot of pressure on the heap by doing a slice query on a large row. Do you have lot of deletes/tombstone on the rows? That might be causing a problem. Also why are you returning so many columns as once, you can use auto paginate feature in Astyanax. Also do you see lot of

Re: crashed while running repair

Looks like memory map failed. In a 64 bit system, you should have unlimited virtual memory but Linux has a limit on the number of maps. Looks at these two places. http://stackoverflow.com/questions/8892143/error-when-opening-a-lucene-index-map-failed https://blog.kumina.nl/2011/04/cassandra-java-i

Re: Heap is not released and streaming hangs at 0%

I will take a heap dump and see whats in there rather than guessing. On Fri, Jun 21, 2013 at 4:12 PM, Bryan Talbot wrote: > bloom_filter_fp_chance = 0.7 is probably way too large to be effective and > you'll probably have issues compacting deleted rows and get poor read > performance with a valu

Re: Updated sstable size for LCS, ran upgradesstables, file sizes didn't change

I think you can remove the json file which stores the mapping of which sstable is in which level. This will be treated by cassandra as all sstables in level 0 which will trigger a compaction. But if you have lot of data, it will be very slow as you will keep compacting data between L1 and L0. This

Re: Timeseries data

I think if you use Level compaction, the number of sstables you will touch will be less because sstables in each level is non overlapping except L0. On Wed, Mar 27, 2013 at 8:20 PM, aaron morton wrote: > sstablekey can help you find which sstables your keys are in. > > But yes, a slice call will

Re: Read during digest mismatch

> > > On Mon, Nov 12, 2012 at 2:49 AM, Jonathan Ellis > wrote: > >> > >> Correct. Which is one reason there is a separate setting for > >> cross-datacenter read repair, by the way. > >> > >> On Thu, Nov 8, 2012 at 4:43 PM, sankalp kohli

Re: Multiple keyspaces vs Multiple CFs

client.insert( > key_user_id, > new ColumnPath("Standard1", null, > "name".getBytes("UTF-8")), > "Chris Goffinet".getBytes("UTF-8"), > timestamp, >

Re: Multiple keyspaces vs Multiple CFs

keyspace aware connection pool. > Edward > > On Thu, Nov 8, 2012 at 5:36 PM, sankalp kohli > wrote: > > Which connection pool are you talking about? > > > > > > On Thu, Nov 8, 2012 at 2:19 PM, Edward Capriolo > > wrote: > >> > >> it is

Read during digest mismatch

Hi, Lets say I am reading with consistency TWO and my replication is 3. The read is eligible for global read repair. It will send a request to get data from one node and a digest request to two. If there is a digest mismatch, what I am reading from the code looks like it will get the data from

Re: Multiple keyspaces vs Multiple CFs

keyspaces would mean > having 10 connection pools. > > On Thu, Nov 8, 2012 at 4:59 PM, sankalp kohli > wrote: > > Is it better to have 10 Keyspaces with 10 CF in each keyspace. or 100 > > keyspaces with 1 CF each. > > I am talking in terms of memory footprint. > >

Multiple keyspaces vs Multiple CFs

Is it better to have 10 Keyspaces with 10 CF in each keyspace. or 100 keyspaces with 1 CF each. I am talking in terms of memory footprint. Also I would be interested to know how much better one is over other. Thanks, Sankalp

Re: Information of Apache Cassandra

It is licensed under Apache so the answer is no. If you are interested, you can read the license agreement on Apache. http://www.apache.org/licenses/LICENSE-2.0.html On Tue, Nov 6, 2012 at 10:35 AM, Manuel Alejandro Ortiz Gil < manuel24or...@gmail.com> wrote: > Hi, I want to use Cassandra for a

Re: Large results and network round trips

I dont have any sample data on this, but read latency will depend on these 1) Consistency level of the read 2) Disk speed. Also you can look at the Netflix client as it makes the co-ordinator node same as the node which holds that data. This will reduce one hop. On Thu, Oct 25, 2012 at 9:04 AM, E

Re: High bandwidth usage between datacenters for cluster

Use placement_strategy = 'org.apache.cassandra.locator.NetworkTopologyStrategy' and also fill the topology.properties file. This will tell cassandra that you have two DCs. You can verify that by looking at output of the ring command. If you DCs are setup properly, only one request will go over WAN