Hi All,
We followed the upgrade guide(
http://www.datastax.com/docs/1.2/install/upgrading) from Datastax web site
and upgraded Cassadra to 1.2.5, but it occurred errors in system.log when
starting up.
After digging into code level, it looks like Cassandra found the file
length of IndexSummary
http://about.me/ColinKuo
Colin Kuo
about.me/ColinKuo
[image: Colin Kuo on about.me]
http://about.me/ColinKuo
On Mon, Jun 9, 2014 at 6:11 AM, Francois Richard frich...@yahoo-inc.com
wrote:
Hi everyone,
We are running some Cassandra clusters (Usually a cluster of 5 nodes
with replication
As Jake suggested, you could firstly increase
compaction_throughput_mb_per_sec and concurrent_compactions to suitable
values if system resource is allowed. From my understanding, major
compaction will internally acquire lock before running compaction. In your
case, there might be a major
You can use nodetool repair instead. Repair is able to re-transmit the
data which belongs to new node.
On Tue, Jun 10, 2014 at 10:40 AM, Mike Heffner m...@librato.com wrote:
Hi,
During an attempt to bootstrap a new node into a 1.2.16 ring the new node
saw one of the streaming nodes
Have you created the schema for these data files? I meant the schema should
be created before you load these data file to C*.
Here is the article for introduction of sstableloader that you could refer.
http://www.datastax.com/documentation/cassandra/1.2/cassandra/tools/toolsBulkloader_t.html
Hi Tim,
The node with IP 94 is leaving. Maybe something wrong happens during
streaming data. You could use nodetool netstats on both nodes to monitor
if there is any streaming connection stuck.
Indeed, you could force remove the leaving node by shutting down it
directly. Then, perform nodetool
Hi,
Can you please firstly check the nodetool compactionstats during repair?
I'm afraid that minor compaction may be blocked by whatever tasks that
causes the number of SStable keep growing.
On Sat, Nov 15, 2014 at 7:47 AM, James Derieg james.der...@uplynk.com
wrote:
Hi everyone,
I'm hoping
Hi,
The feature of speculative execution in Cassandra 2.0 helps in this case.
You can get further explanation on below link.
http://www.datastax.com/dev/blog/rapid-read-protection-in-cassandra-2-0-2
Thanks!
On Tue, Dec 6, 2016 at 10:13 AM, Sungju Hong wrote:
> Hello,
>
>