I should clarify that we are running Cassandra 1.1.12.
Dave
On Fri, Oct 4, 2013 at 2:08 PM, Dave Cowen wrote:
> We're testing expanding a 4-node cluster into an 8-node cluster, and we
> keep running into issues with the repair process near the end.
>
> We're bringing up nodes 1-by-1 into the c
We're testing expanding a 4-node cluster into an 8-node cluster, and we
keep running into issues with the repair process near the end.
We're bringing up nodes 1-by-1 into the cluster, retokening nodes for an
8-node configuration, running nodetool cleanup on the nodes after each
retokening, and the
On 10/04/2013 11:46 AM, Baskar Duraikannu wrote:
Good evening. We are using Cassandra for a while. I have been faced
with a question "why did facebook drop Cassandra" over and over again. I
could not find a good answer to this question on the internet.
Could you please help me with the question
For the record, I was depending on a project that was pulling in an older
r09 version of Guava. Thanks again for the help.
On Thu, Oct 3, 2013 at 7:29 PM, Richard Rodseth wrote:
> Thanks very much. Your pom works for me too, so that gives me a good
> reference point.
>
>
> On Thu, Oct 3, 2013 a
Good evening. We are using Cassandra for a while. I have been faced with a
question "why did facebook drop Cassandra" over and over again. I could not
find a good answer to this question on the internet.
Could you please help me with the question?
--RegardsBaskar Duraikannu
One more piece of information to help troubleshooting the issue:
During the "nodetool drain" operation just before the upgrade, instead of
just stopping accepting new writes, the node actually shuts itself down.
This bug was also reported in this other thread:
http://mail-archives.apache.org/mod_m
On Fri, Oct 4, 2013 at 9:09 AM, Paulo Motta wrote:
> I manually tried to insert and retrieve some data into both the newly
> upgraded nodes and the old nodes, and the behavior was very unstable:
> sometimes it worked, sometimes it didn't (TimedOutException), so I don't
> think it was a network pro
Hello,
I have isolated one of our data centers to simulate a rolling restart
upgrade from C* 1.1.10 to 1.2.10. We replayed our production traffic to the
C* nodes during the upgrade and observed an increased number of read
timeouts during the upgrade process.
I executed nodetool drain before upgra
Hi
I there a way to obfuscate the keystore/truststore password?
Thanks
Shahryar
--
Yes, what is Solr Cloud then for, that already provides clustering support,
so what's the need for Cassandra ?
On Tue, Oct 1, 2013 at 2:06 AM, Sávio Teles wrote:
>
> Solr's index sitting on a single machine, even if that single machine can
>> vertically scale, is a single point of failure.
>>
>
Here.
We have 1.5 TB running smooth. index_interval: 1024 and 8GB JVM. Default
bloomfilters.
The only pb we have is that We have 2TB SSD so they are almost full, C*
starts crashing. It looks like cassandra consider there is no more space
available, when there is still 500GB available (You're not s
That spreadsheet doesn't take compression into account, which is very
important in my case. Uncompressed, my data is going to require a
petabyte of storage according to the spreadsheet. I am pretty sure I
won't get that much storage to play with.
The spreadsheet also shows that Cassandra waste
12 matches
Mail list logo
