Wed, Mar 28, 2012 at 2:57 PM, Sanjeev Kulkarni wrote:
> Hey guys,
> We have a fresh 4 node 0.8.10 cluster that we want to pump lots of data
> into.
> The data resides on 5 data machines that are different from Cassandra
> nodes. Each of these data nodes has 7 disks where the data resi
Hey guys,
We have a fresh 4 node 0.8.10 cluster that we want to pump lots of data into.
The data resides on 5 data machines that are different from Cassandra
nodes. Each of these data nodes has 7 disks where the data resides.
In order to get maximum load performance, we are assigning 7 ips to
each
> Cheers
>
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 16/03/2012, at 10:04 AM, Sanjeev Kulkarni wrote:
>
> Hi,
> I&
Hi,
I'm using a 4 node cassandra cluster running 0.8.10 with rf=3. Its a brand
new setup.
I have a single col family which contains about 10 columns. I have enabled
secondary indices on 3 of them. I used sstableloader to bulk load some data
into this cluster.
I poked around the logs and saw the fol
, Thamizh wrote:
> please check [default@unknown] help create column family;
> These are default values, until you explicitly mentioned on CF creation.
>
> Regards,
> Thamizhannal
> ------
> *From:* Sanjeev Kulkarni
> *To:* user@cassandra.apache.or
Hey guys,
I'm using a three node cluster running 0.8.6 with rf of 3. Its a freshly
installed cluster with no upgrade history.
I have 6 cfs and only one of them is written into. That cf has around one
thousand keys. A quick key_range_scan verifies this.
However when I do cfstats, I see the following
Hey guys,
Are there any side-effects of increasing
the thrift_framed_transport_size_in_mb and thrift_max_message_length_in_mb
variables from their default values to something like 100mb?
Thanks!
Hey guys,
We are designing our data model for our app and this question came up.
Lets say that I have a large number of rows(say 1M). And just one column
family.
Each row contains either columns (A, B, C) or (X, Y, Z). I want to run a
get_range_slices query to fetch columns (A, B, C).
Does cassandr
Here is the snapshot of the logs from one of the machine between the time
when I mailed to when it finally started to look at the commitlogs. At the
end you can see that it is discarding obsolete commitlogs. Not sure what
that means.
INFO [HintedHandoff:1] 2011-05-17 01:17:10,510 ColumnFamilyStor
Its now almost 4 hours. I still see commitlogs worth 1.2G on the machines. I
see no activity
On Mon, May 16, 2011 at 6:33 PM, Sanjeev Kulkarni wrote:
> After I updated the memtable_throughput, I stopped all my writing
> processes. I did a du /commitlog to find how much was cassandra commit
44 PM, Sanjeev Kulkarni wrote:
> Hey guys,
> I have updated all my column families with 32 as the memtable_throughput. I
> will let you know how cassandra behaves.
> Thanks!
>
>
> On Mon, May 16, 2011 at 3:52 PM, mcasandra wrote:
>
>> You can try to update column fam
Hey guys,
I have updated all my column families with 32 as the memtable_throughput. I
will let you know how cassandra behaves.
Thanks!
On Mon, May 16, 2011 at 3:52 PM, mcasandra wrote:
> You can try to update column family using cassandra-cli. Try to set
> memtable_throughput to 32 first.
>
> [d
Hi,
Are you referring to the binary_memtable_throughput_in_mb which is a global
parameter or the per col fam specific memtable_throughput_in_mb? The former
is set to 256 and we dont override the default col fam specific value. Would
just re-setting the global binary_memtable_throughput_in_mb to som
our write happen in bursts. So often times, clients write data as fast as
they can. Conceivably one can write 5G in one hour.
The other setting that we have is that our replication factor is 3 and we
write using QUORUM. Not sure if that will affect things.
On Fri, May 13, 2011 at 12:04 AM, Peter S
Hi Peter,
Thanks for the response.
I haven't explictly set a value for the memtable_flush_after_mins parameter.
Looks like the default is 60minutes.
I will try to play around this value to see if that fixes things.
Thanks again!
On Thu, May 12, 2011 at 11:41 AM, Peter Schuller <
peter.schul...@inf
Hey guys,
I have a ec2 debian cluster consisting of several nodes running 0.7.5 on
ephimeral disks.
These are fresh installs and not upgrades.
The commitlog is set to the smaller of the disks which is around 10G in size
and the datadir is set to the bigger disk.
The config file is basically the sam
Hi Adam,
We have been facing some similar issues of late. Wondering if Jonathan's
suggestions worked for you.
Thanks!
On Sat, May 7, 2011 at 6:37 PM, Jonathan Ellis wrote:
> The live:serialized size ratio depends on what your data looks like
> (small columns will be less efficient than large blo
ining
>
> Adding the fourth node to the cluster with an empty schema using
> auto_bootstrap was not successful. A nodetool netstats on the new node
> shows “Mode: Joining: getting bootstrap token” similar to what the third
> node did before it was manually added. Also, there are no
e did before it was manually added. Also, there are no exceptions in the
> logs but it never joins the ring.
>
>
>
> *From:* Sanjeev Kulkarni [mailto:sanj...@locomatix.com]
> *Sent:* Thursday, May 05, 2011 11:47 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: New node not
dded fine. I'm
> bringing up a 4th node now and will see if it has the same problem auto
> bootstrapping.
>
> ------
> *From:* Sanjeev Kulkarni [sanj...@locomatix.com]
> *Sent:* Thursday, May 05, 2011 2:18 AM
> *To:* user@cassandra.apache.org
> *
Hey guys,
I'm running into what seems like a very basic problem.
I have a one node cassandra instance. Version 0.7.5. Freshly installed.
Contains no data.
The cassandra.yaml is the same as the default one that is supplied, except
for data/commitlog/saved_caches directories.
I also changed the addre
, Jonathan Ellis wrote:
> No. You'll need to run scrub.
>
> On Mon, Apr 25, 2011 at 11:19 PM, Sanjeev Kulkarni
> wrote:
> > Hi,
> > Thanks for pointing out the fix. My followup question is if I install
> 0.7.5
> > will the problem go away with the curren
> On Mon, Apr 25, 2011 at 9:47 PM, Sanjeev Kulkarni
> wrote:
> > The only other interesting information is that the columns of these rows
> all
> > had some ttl attached to them. Not sure if that matters.
> > Thanks!
> >
> > On Mon, Apr 25, 2011 at 5:27 PM
ither the
>> length was
>> >> wrong or the row was missing data as there was was no extra data in the
>> row
>> >> after the last column.
>> >> This was however on a somewhat aging dataset, so suspected it could be
>> >> related to 2376.
.
>> This was however on a somewhat aging dataset, so suspected it could be
>> related to 2376.
>>
>> Playing around with 0.8 at the moment and not seen it there yet (bet it
>> will show up tomorrow once I wrote that.. :))
>> Terje
>>
>> On Tue, Apr 26, 20
Mon, Apr 25, 2011 at 5:54 AM, Sanjeev Kulkarni
> wrote:
> > Hey guys,
> > Running a one node cassandra server with version 0.7.4 patched
> > with https://issues.apache.org/jira/browse/CASSANDRA-2376
> > The system was running fine for a couple of days when we started not
Hey guys,
Running a one node cassandra server with version 0.7.4 patched with
https://issues.apache.org/jira/browse/CASSANDRA-2376
The system was running fine for a couple of days when we started noticing
something strange with cassandra. I stopped all applications and restarted
cassandra. And the
(https://issues.apache.org/jira/browse/CASSANDRA-2376), but not one
> that would cause a crash. Actual process death is only caused by (a)
> running out of memory or (2) JVM bugs.
>
> On Wed, Mar 23, 2011 at 9:17 PM, Sanjeev Kulkarni
> wrote:
> > Hey guys,
> > I have a
Hey guys,
I have a one node system(with replication factor of 1) running cassandra.
The machine has two disks. One is used as the commitlog and the other as
cassandra's data directory. The node just had gotten unresponsive and had to
be hard rebooted.
After restart, cassandra started off fine. But
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
On Tue, Mar 15, 2011 at 2:27 PM, Jonathan Ellis wrote:
> Did you upgrade from an earlier version? Did you read NEWS.txt?
>
> On Tue, Mar 15, 2011 at 4:21 P
Hey guys,
Have started facing a crash in my cassandra while reading. Here are the
details.
1. single node. replication factor of 1
2. Cassandra version 0.7.3
3. Single keyspace. 5 column families.
4. No super columns
5. My data model is a little bit skewed. It results in having several small
rows a
31 matches
Mail list logo
