But I think use SSD can boost read performance, this is the main problem now
for us to use Cassandra.
On Tue, Jun 8, 2010 at 10:16 PM, Jonathan Ellis wrote:
> cassandra is designed to do less random i/o than b-tree based systems
> like tokyo cabinet. ssds are not as useful for most workloads.
>
It needs a SliceRange. For example:
SliceRange range = new SliceRange(); range.setStart("".getBytes());
range.setFinish("".getBytes()); range.setReversed(true); range.setCount(20);
SlicePredicate sp = new SlicePredicate(); sp.setSlice_range(range);
client.get_slice(KEYSPACE, KEY, ColumnParent, sp,
try specify the InitialToken.
In your cluster, set the token to i*(2**127/6), i = [1,6]. It will helps.
On Sat, May 1, 2010 at 8:03 AM, elsif wrote:
> I upgraded to 0.6.1 and was able to bring up all the nodes and make
> queries.
>
> After adding some new data, the java vm ran out of memory on t
52
On Tue, Apr 27, 2010 at 10:53 AM, Chris Goffinet wrote:
> I'll work on doing more tests around this. In 0.5 we used a different data
> structure that required polling. But this does seem problematic.
>
> -Chris
>
> On Apr 26, 2010, at 7:04 PM, Eric Yu wrote:
>
I have the same problem here, and I analysised the hprof file with mat, as
you said, LinkedBlockQueue used 2.6GB.
I think the ThreadPool of cassandra should limit the queue size.
cassandra 0.6.1
java version
$ java -version
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b
.6 anyway.
>
> On Sat, Mar 27, 2010 at 8:51 PM, Eric Yu wrote:
> > And one more clue here, when ReplicateFactor is 1, it's OK, after changed
> to
> > 2, the exception occurred.
> >
> > On Sun, Mar 28, 2010 at 9:46 AM, Eric Yu wrote:
> >>
> >>
And one more clue here, when ReplicateFactor is 1, it's OK, after changed to
2, the exception occurred.
On Sun, Mar 28, 2010 at 9:46 AM, Eric Yu wrote:
> Hi Jonathan,
>
> I upgraded my jdk to latest version, and I am sure I start Cassandra with
> it (set JAVA_HOME in cassansra.
;
> On Sat, Mar 27, 2010 at 10:55 AM, Eric Yu wrote:
> > Hi, list
> > I got this exception when insert into a cluster with 5 node, is this a
> bug
> > or something else is wrong.
> >
> > here is the system log:
> >
> > INFO [GMFD:1] 2010-03-
Jonathan, thanks for your quick reply. I'll have a try now.
On Sun, Mar 28, 2010 at 12:02 AM, Jonathan Ellis wrote:
> This means you need to upgrade your jdk to build 18 or later
>
> On Sat, Mar 27, 2010 at 10:55 AM, Eric Yu wrote:
> > Hi, list
> > I got this ex
Hi, list
I got this exception when insert into a cluster with 5 node, is this a bug
or something else is wrong.
here is the system log:
INFO [GMFD:1] 2010-03-27 23:15:16,145 Gossiper.java (line 543) InetAddress
/172.19.15.210 is now UP
ERROR [Timer-1] 2010-03-27 23:23:27,739 TcpConnection.java (
10 matches
Mail list logo
