We have a 12node Cassandra cluster running on 1.2.12. Each node is using 1.1TB
out of 2TB. Each node has a min+max heap of 24Gb and the physical server has
48Gb. Our nodes do not restart during the week, only on the weekend, and we're
observing that the off heap memory that is consumed ramps
Agreed. We only use secondary indexes for column families that are relatively
small (~5k rows). For anything larger, we store the data into a wide row (but
this depends on your data model)
-Original Message-
From: jonathan.had...@gmail.com [mailto:jonathan.had...@gmail.com] On Behalf
After we dropped a table, we noticed that the sstables are still there. After
searching through the forum history, I noticed that this is known behavior.
1) Is there any negative impact of deleting the sstables off disk and then
restarting Cassandra?
2) Are there any other recommend
nd have no effect on gossip
marking a node as down, in which case the streaming session will remain intact.
The side effect of long GC's is increased latency from that node during that
period.
Mark
On Wed, Jul 30, 2014 at 2:24 PM, Parag Patel
mailto:ppa...@clearpoolgroup.com>> wrote:
A
increasing the phi value would reduce the chance of a node in the ring being
marked down during a heavy gc cycle.
Mark
On Wed, Jul 30, 2014 at 1:41 PM, Parag Patel
mailto:ppa...@clearpoolgroup.com>> wrote:
Mark,
I see this output my log many times over for 2 nodes. We have a cron e
pping
process again
Mark
On Wed, Jul 30, 2014 at 12:03 PM, Parag Patel
mailto:ppa...@clearpoolgroup.com>> wrote:
Thanks for the detailed response. I checked ‘nodetool netstats’ and I see
there are pending streams, all of which are stuck at 0%. I was expecting to
see at least one outp
des to spread the data so
you stream less in future.
Finally you could upgrade to 2.0.x as it contains a complete refactor of
streaming and should make your streaming sessions more robust and transparent:
https://issues.apache.org/jira/browse/CASSANDRA-5286
Mark
On Wed, Jul 30, 201
Hi,
I've noticed that our datamodel has many unnecessary secondary indexes. Are
there a recommended procedure to drop a secondary index on a very large table?
Is there any sort of repair/cleanup that should be done after calling the DROP
command?
Thanks,
Parag
Hi,
It's taking a while to boostrap a 13th node into a 12 node cluster. The
average node size is about 1.7TB. At the beginning of today we were close to
.9TB on the new node and 12 hours later we're at 1.1TB. I figured it would
have finished by now because when I was looking on OpsCenter, th
: Parag Patel [mailto:ppa...@clearpoolgroup.com]
Sent: Wednesday, July 16, 2014 5:22 PM
To: user@cassandra.apache.org
Subject: RE: adding more nodes into the cluster
Thanks rob
From: Robert Coli [mailto:rc...@eventbrite.com]
Sent: Wednesday, July 16, 2014 2:21 PM
To: user@cassandra.apache.org
Thanks rob
From: Robert Coli [mailto:rc...@eventbrite.com]
Sent: Wednesday, July 16, 2014 2:21 PM
To: user@cassandra.apache.org
Subject: Re: adding more nodes into the cluster
On Wed, Jul 16, 2014 at 9:16 AM, Parag Patel
mailto:ppa...@clearpoolgroup.com>> wrote:
We have a 12 node cluste
Hi,
We have a 12 node cluster with replication factor of 3 in 1 datacenter. We
want to add 6 more nodes into the cluster. I'm trying to see what's better
bootstapping all 6 at the same time or doing it one node at a time.
Anybody have any thoughts on this?
Thanks,
Parag
In your scenario #1, is the total number of nodes staying the same? Meaning,
if you launch multiple clusters for #2, you’d have N total nodes – are we
assuming #1 has N or less than N?
If #1 and #2 both have N, wouldn’t the performance be the same since
Cassandra’s performance increases linear
tion
Data structures that are stored off heaps:
1) Row cache (if JNA enabled, otherwise on heap)
2) Bloom filter
3) Compression offset
4) Key Index sample
On heap:
1) Memtables
2) Partition Key cache
Hope that I did not forget anything
Regards
Duy Hai DOAN
On Thu, Apr 10, 2014 at 9:13 PM, P
We're using Cassandra 1.2.12. What aspects of the data is stored in off heap
memory vs heap memory?
orks. I believe the difference between periodic and batch is just that
-- if it is periodic, it will fsync every 10 seconds, if it is batch it will
fsync if there were any changes within a time window.
On 2014-04-09 10:06:52 +0000, Parag Patel said:
>
>>>>> 1) Why is the
1) Why is the default 4GB? Has anyone changed this? What are some aspects
to consider when determining the commitlog size?
2) If the commitlog is in periodic mode, there is a property to set a time
interval to flush the incoming mutations to disk. This implies that there is a
queu
Nate,
What values for the FlushWriter line would draw concern to you? What is the
difference between Blocked and All Time Blocked?
Parag
From: Nate McCall [mailto:n...@thelastpickle.com]
Sent: Thursday, February 27, 2014 4:22 PM
To: Cassandra Users
Subject: Re: Commit logs building up
What wa
at 11:38 am, Parag Patel
mailto:parag.pa...@fusionts.com>> wrote:
Thanks for that link.
Our 1.2 version is 1.2.12
Our 2.0.3 nodes were restarted once. Before restart, it was the 1.2.12 binary,
after it was the 2.0.3. Immediately after the node was back in the cluster, w
Hi,
I'm using Astyanax and trying to do search for multiple keys with pagination.
I tried ".getKeySlice" with a list a of primary keys, but it doesn't allow
pagination. Does anyone know how to tackle this issue with Astyanax?
Parag
d for each node?
From: Robert Coli [mailto:rc...@eventbrite.com]
Sent: Thursday, December 19, 2013 4:17 PM
To: user@cassandra.apache.org
Subject: Re: Issue upgrading from 1.2 to 2.0.3
On Thu, Dec 19, 2013 at 1:03 PM, Parag Patel
mailto:parag.pa...@fusionts.com>> wrote:
We are in the
Hi,
We are in the process of upgrading 1.2 to 2.0.3. We have a four node cluster
and we're upgrading one node at a time. After upgrading two of the nodes, we
encountered a problem. We observed that if we run nodetool status on the 2.0.3
hosts, they would show 2 nodes down and 2 nodes up. If
Hi,
I'm looking for a way to view statistics. Mainly, I'd like to see the
distribution of writes and reads over the course of a day or a set of days. Is
there a way to do this through nodetool or by downloading a utility?
Thanks,
Parag
run a repair to get
the missing data.
On Mon, Sep 16, 2013 at 8:12 AM, Parag Patel
mailto:parag.pa...@fusionts.com>> wrote:
RF=3. Single dc deployment. No v-nodes.
Is there a certain amount of time I need to wait from the time the down node is
started to the point where it's ready
From: sankalp kohli [mailto:kohlisank...@gmail.com]
Sent: Sunday, September 15, 2013 4:52 PM
To: user@cassandra.apache.org
Subject: 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
Hi,
We have a six node cluster running DataStax Community Edition 1.2.9. From our
app, we use the Netflix Astyanax library to read and write records into our
cluster. We read and write with QUARUM. We're experiencing an issue where
when a node goes down, we see our read queries slowing down
26 matches
Mail list logo