Thanks Jonathan and Cassandra PMC,
I am all set for 2.0 :)
Regards,
On Thu, Jan 12, 2012 at 10:06 PM, Jonathan Ellis wrote:
> The Apache Cassandra PMC has voted to add Vijay as a committer. Thank
> you Vijay, and we look forward to continuing to work with you!
>
> --
> Jonathan Ellis
> Proj
The Apache Cassandra PMC has voted to add Vijay as a committer. Thank
you Vijay, and we look forward to continuing to work with you!
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com
The serializing cache is basically optimal. Your problem is really
that row cache is not designed for wide rows at all. See
https://issues.apache.org/jira/browse/CASSANDRA-1956
On Thu, Jan 12, 2012 at 10:46 PM, Todd Burruss wrote:
> after looking through the code it seems fairly straight forwar
after looking through the code it seems fairly straight forward to create
some different cache providers and try some things.
has anyone tried ehcache w/o persistence? I see this JIRA
https://issues.apache.org/jira/browse/CASSANDRA-1945 but the main
complaint was the disk serialization, which I d
I can't use SerializedCacheProvider with wide rows. My tests show the
performance of it is rediculously slow because of the copying to heap for each
get
Sent from my Android phone using TouchDown (www.nitrodesk.com)
-Original Message-
From: Jonathan Ellis [jbel...@gmail.com]
Received: T
thx for the info. I'm a bit leary on the memcached (or any out-of-process
cache) because of coherency issues:
https://issues.apache.org/jira/browse/CASSANDRA-2701
On 1/12/12 5:50 PM, "Bruno Leonardo Gonçalves" wrote:
>Twitter engineers reported a similar experience [1] (slide 32). They
>mana
Hi Eric,
Thanks for the follow up. I see the point of "increased complexity on
the clients" keep coming up in the references, but the truth is that
we've pretty much all had to abstract serialization to some degree or
another just to keep up with changes. At least in the case of Hector,
dealing dir
8x is pretty normal for JVM and bookkeeping overhead with the CLHCP.
The SerializedCacheProvider is the default in 1.0 and is much lighter-weight.
On Thu, Jan 12, 2012 at 6:07 PM, Todd Burruss wrote:
> I'm using ConcurrentLinkedHashCacheProvider and my data on disk is about 4gb,
> but the RAM u
Twitter engineers reported a similar experience [1] (slide 32). They
managed to reduce by 45% memory usage with cache provider backed by
Memcached. Lately I've been worrying a lot with the swelling of Java
objects. In 64-bit servers are tried using the JVM option
-XX:+UseCompressedOops? This presen
I'm using ConcurrentLinkedHashCacheProvider and my data on disk is about 4gb,
but the RAM used by the cache is around 25gb. I have 70k columns per row, and
only about 2500 rows – so a lot more columns than rows. has there been any
discussion or JIRAs discussing reducing the size of the cache?
On Tue, Jan 10, 2012 at 11:40 PM, Dave Brosius wrote:
> Greetings,
>
> I wanted to mention this to folks who may be running into this issue. A
> user on IRC reporting that cloning the cassandra repo on the apache servers
>
> http://git-wip-us.apache.org/repos/asf/cassandra.git
>
> fails with err
On Thu, Jan 12, 2012 at 6:07 PM, Jonathan Ellis wrote:
> Sorry to be That Guy, but CASSANDRA-3733 (just fixed by Brandon) can
> cause OOM during hint replay similar to the ones in CASSANDRA-3681.
Ok, I'll rerolled. The vote is thus closed and I'll start a new one
with CASSANDRA-3681
(and probably
On Thu, Jan 12, 2012 at 4:40 PM, paul cannon wrote:
> On Jan 12, 2012, at 5:36 AM, Sylvain Lebresne wrote:
>> Note that I had to adapt a little bit to the switch to git. In particular,
>> instead of using sha1 to mark the tentative commit of a release, I've decided
>> to use a lightweight tag, na
Sorry to be That Guy, but CASSANDRA-3733 (just fixed by Brandon) can
cause OOM during hint replay similar to the ones in CASSANDRA-3681.
On Thu, Jan 12, 2012 at 5:36 AM, Sylvain Lebresne wrote:
> It's a new year, quite a bunch of fixes since 1.0.6, feels like it's time to
> do a new release. I th
On Jan 12, 2012, at 5:36 AM, Sylvain Lebresne wrote:
> Note that I had to adapt a little bit to the switch to git. In particular,
> instead of using sha1 to mark the tentative commit of a release, I've decided
> to use a lightweight tag, namely 1.0.7-tentative. My goal being that once the
> vote p
On 12 January 2012 13:27, Sylvain Lebresne wrote:
> On Thu, Jan 12, 2012 at 12:56 PM, Stephen Connolly
> wrote:
>> -0: H may have to rework somewhat the pom generation now that
>> moved to GIT...
>>
>> e.g. see
>> https://repository.apache.org/content/repositories/orgapachecassandra-057/o
On Thu, Jan 12, 2012 at 12:56 PM, Stephen Connolly
wrote:
> -0: H may have to rework somewhat the pom generation now that
> moved to GIT...
>
> e.g. see
> https://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-parent/1.0.7/cassandra-parent-
-0: H may have to rework somewhat the pom generation now that
moved to GIT...
e.g. see
https://repository.apache.org/content/repositories/orgapachecassandra-057/org/apache/cassandra/cassandra-parent/1.0.7/cassandra-parent-1.0.7.pom
at XPath /project/scm
Those are SVN urls... should be git
It's a new year, quite a bunch of fixes since 1.0.6, feels like it's time to
do a new release. I thus propose the following artifacts for release as 1.0.7.
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.0.7-tentative
Artifacts:
https://repository.apache.org/
19 matches
Mail list logo
