We are running 0.8.7. No big issues so far.
Thanks,
Jahangir.
On Tue, Dec 6, 2011 at 5:05 PM, Pierre Chalamet pie...@chalamet.net wrote:
Hello,
** **
Recent problems with Cassandra 1.0.x versions seems to tell it is still
not ready for prime time.
** **
We are currently using
Tombstone is a marker indicating the record to be deleted.
gc_grace_seconds is the time after which the record will be deleted
physically from the node.
There is no ad-hoc way of gc'ing tombstones. Only after gc_grace_seconds
the tombstones will be gc'ed.
Thanks,
Jahangir Mohammed.
On Thu
Yes, mostly sounds like it. In our case failed repairs were causing
accumulation of the tmp files.
Thanks,
Jahangir Mohammed.
On Thu, Dec 1, 2011 at 2:43 PM, Alexandru Dan Sicoe
sicoe.alexan...@googlemail.com wrote:
Hi Jeremiah,
My commitlog was indeed on another disk. I did what you said
Do you use any client which gives you this timeout ?
If you don't specify any timeout from client, look at rpc_timeout_in_ms.
Increase it and see if you still suffer this.
Repair is a costly process.
Thanks,
Jahangir Mohammed.
On Thu, Nov 24, 2011 at 2:45 AM, Patrik Modesto patrik.mode
often.
Regards
Patrik
Dne 24.11.2011 15:00 Jahangir Mohammed md.jahangi...@gmail.com
napsal(a):
Do you use any client which gives you this timeout ?
If you don't specify any timeout from client, look at rpc_timeout_in_ms.
Increase it and see if you still suffer this.
Repair is a costly
That will give you a snapshot of thread pools. You should look at
ROW-READ-STAGE and see pending and active. If there are many pending, it
means that the cluster is not able to keep up with the read requests coming
along.
Thanks,
Jahangir Mohammed.
On Thu, Nov 24, 2011 at 2:14 PM, Patrik Modesto
you want to store data
as per I.P. (geo location data) ..Anyways, it was not very clear from your
question what you are trying to do.
Thanks,
Jahangir Mohammed.
On Tue, Nov 22, 2011 at 7:57 PM, Mathieu Lalonde mrlalo...@live.ca wrote:
Hi,
I am wondering if Cassandra's features
I am not so sure from version to version.
1. Which client are you using? Any custom load balancer?
2. Is the hardware on this node any different from other nodes?
Thanks,
Jahangir.
On Mon, Nov 21, 2011 at 5:55 AM, Johann Höchtl h.hoec...@ic-drei.de wrote:
Hi all,
I'm experiencing strange
Hmm..What's the data distribution like on cluster? R.P.?
On Mon, Nov 21, 2011 at 7:31 AM, Johann Höchtl h.hoec...@ic-drei.de wrote:
**
I'm using hector-0.8.0-2.
No custom load balancer.
Hardware is equal on every server.
Am 21.11.2011 13:26, schrieb Jahangir Mohammed:
I am not so sure
IMHO, you should start with something very simple RDBMS and meanwhile
getting handle over Cassandra or other noSql technology. Start out with
simple, but always be aware and conscious of the next thing you will have
in stack. It's timetaking to work with new technology if you are in the
phase of
There is something wrong with the system. Your benchmarks are way off. How
are you benchmarking? Are you using the stress lib included?
On Nov 19, 2011 8:58 PM, Kent Tong freemant2...@yahoo.com wrote:
Hi,
On my computer with 2G RAM and a core 2 duo CPU E4600 @ 2.40GHz, I am
testing the
Mostly, they are I/O and CPU intensive during major compaction. If ganglia
doesn't have anything suspicious there, then what is performance loss ?
Read or write?
On Nov 17, 2011 1:01 PM, Maxim Potekhin potek...@bnl.gov wrote:
In view of my unpleasant discovery last week that deletions in
Hello All,
JVM is crashing on the cassandra nodes. Re-start doesn't help for long.
Ring information:
$ bin/nodetool -h A ring;
Address DC RackStatus State LoadOwns
Token
127605887595351923798765477786913079297
A DC1 RAC1Up
Thanks. Will try upgrading jvm.
Is 1.0 or 0.8.6 is backwards compatible with 0.8.1?
Thanks,
Jahangir.
On Wed, Nov 2, 2011 at 9:39 AM, Sylvain Lebresne sylv...@datastax.comwrote:
On Wed, Nov 2, 2011 at 2:03 PM, Jahangir Mohammed
md.jahangi...@gmail.com wrote:
Hello All,
JVM is crashing
Have this weird issue. Initially, it was jvm crashing with Segmentation
fault errors. Once I updated it, it did solve the problem that jvm isn't
crashing. This time cassandra process just dies without any warning in the
logs.
To note specifics of the node:
98GB RAM
400 GB Disk Space
Currently
15 matches
Mail list logo
