FYI, when I increase the test memory to 1G to resemble the default setting
in cassandra the OOM doesn't happen, so that's a non-issue.
On Sat, Sep 18, 2010 at 9:02 PM, Ran Tavory wrote:
> I haven't tried the python tests. What's also interesting is that if I
> run a single java test case then th
I haven't tried the python tests. What's also interesting is that if I
run a single java test case then there's no oom. Only when I run the
entire class then I get it. Also if I ads random sleeps then there is
no oom but other more interesting errors surface.
On Saturday, September 18, 2010, Nate
Ran, have you tried to reproduce this using cassandra's python system
tests? Those have coverage of the system methods as well.
On 9/18/10, Nate McCall wrote:
> An additional point - we just added the system_* methods and this test
> class does an add, rename then drop for both CF and keyspace.
>
actually the tests are forked so the memory settings need to be set at the
pom.xml file and not by using maven_opts as I did. Ill experiment some more.
> An additional point - we just added the system_* methods and this test
> class does an add, rename then drop for both CF and keyspace.
>
> On 9/
An additional point - we just added the system_* methods and this test
class does an add, rename then drop for both CF and keyspace.
On 9/18/10, Ran Tavory wrote:
> I started seeing OOM when running hector's unit-tests on 0.7.0. The OOM is
> in cassandra's code so either there had been recent cha
I started seeing OOM when running hector's unit-tests on 0.7.0. The OOM is
in cassandra's code so either there had been recent changes within cassandra
or it's just that we added new coverage which causes this OOM.
On my mac it's 100% repro but other hector devs have reported they don't get
this O
