Graham,
This is largely fixed in 2.1 with the introduction of partially off-heap
memtables - the slabs reside off-heap, so do not cause any GC issues.
As it happens the changes would also permit us to recycle on-heap slabs
reasonable easily as well, so feel free to file a ticket for that,
Just to be clear, I'm not strongly opposed to having CQL tests in the unit
tests suite per-se (I happen to find dtests easier to work with, probably
because I don't use debuggers, but I'm good with saying that this just mean
I'm crazy and shouldn't be taken into account). Having tests that are
The standard reasoning for unit tests is specificity of errors. Well
written tests suites tell you where you screwed up exactly just by the
success and failure pattern, often cutting down the need for a debugger.
System tests standard rational is validating these units are wired up
correctly.
Since we closed the first try we've fixed even more bugs, with notable
things
like CASSANDRA-6285. In any case, that changelog is getting pretty damn
long so
I propose the following artifacts for release as 2.0.8.
sha1: 484d2816940cd2eb22d2365fcb376dd27e059e2e
Git:
One of the reasons it is so long is because there are quite a few duplicate
entries.
* (Hadoop) support authentication in CqlRecordReader (CASSANDRA-7221)
* (Hadoop) Close java driver Cluster in CQLRR.close (CASSANDRA-7228)
* Fix potential SlabAllocator yield-starvation (CASSANDRA-7133)
* Warn
On Wed, May 21, 2014 at 11:34 AM, Jonathan Ellis jbel...@gmail.com wrote:
Which of those could someone else help with?
I'll take CASSANDRA-7120 (and CASSANDRA-7267, if needed).
--
Tyler Hobbs
DataStax http://datastax.com/
We need to add 7245 to that list. I'll try to get to it tomorrow.
On 21 May 2014 17:40, Tyler Hobbs (JIRA) j...@apache.org wrote:
[
https://issues.apache.org/jira/browse/CASSANDRA-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
Tyler Hobbs reassigned
+1
On Wed, May 21, 2014 at 10:32 AM, Mikhail Stepura
mikhail.step...@outlook.com wrote:
+1
-M
On May 21, 2014, at 6:19, Sylvain Lebresne sylv...@datastax.com wrote:
Since we closed the first try we've fixed even more bugs, with notable
things
like CASSANDRA-6285. In any case, that
+1
On Wed, May 21, 2014 at 8:19 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Since we closed the first try we've fixed even more bugs, with notable
things
like CASSANDRA-6285. In any case, that changelog is getting pretty damn
long so
I propose the following artifacts for release as
+1
On Wed, May 21, 2014 at 8:19 AM, Sylvain Lebresne sylv...@datastax.comwrote:
Since we closed the first try we've fixed even more bugs, with notable
things
like CASSANDRA-6285. In any case, that changelog is getting pretty damn
long so
I propose the following artifacts for release as
On Wed, May 21, 2014 at 4:06 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Having tests that are
intrinsically
the same kind of tests in two places bugs me a bit more however.
I do think that CQL tests in general make more sense as unit tests,
but I'm not so anal that I'm going to insist
Thanks so much for the info…
I will read the relevant code and/or JIRA issues since I’m not sure what the
trigger for on/off heap is yet, and maybe open a ticket for recycling.
Hopefully in the short term we can mitigate our fragmentation problem trivially
- we upped JVM memory on some nodes
12 matches
Mail list logo
