Hello all,
I have a small dev environment with 4 machines. One of them, I had it
removed (.33) from the cluster because I wanted to upgrade its HD to a SSD.
I then reinstalled it and tried to join. It is on UJ status for a week now
and no changes.
I had tried node-repair etc but nothing.
nodetoo
I had logged a bug on JIRA as I think it might be a better way of reporting
this: https://issues.apache.org/jira/browse/CASSANDRA-10861
On Mon, Dec 14, 2015 at 1:52 PM, Carlos A wrote:
> Hello all,
>
> We had upgrade to Cassandra 3.0.0 and later to 3.0.1. That went well.
> System
at 12:52 PM, Carlos A wrote:
>
>> We had upgrade to Cassandra 3.0.0 and later to 3.0.1. That went well.
>> System seems stable.
>>
>
>
> https://www.eventbrite.com/engineering/what-version-of-cassandra-should-i-run/
>
> Running cutting edge versions of server a
Hello all,
We had upgrade to Cassandra 3.0.0 and later to 3.0.1. That went well.
System seems stable.
However we have a Spring API that uses Cassandra and has a connection pool
using the com.datastax.cassandra driver. We had to upgrade that as well as
it would not work with the latest driver to C
gt; It seems likely either your snitch changed, your properties changed, or
> something caused Cassandra to think one of the two happened...
>
> What's your node layout?
>
> On Fri, Nov 27, 2015 at 6:45 PM, Carlos A wrote:
>
>> Hello all,
>>
>> I had 2
Hello all,
I had 2 of my systems upgraded to 3.0 from the same previous version.
The first cluster seem to be fine.
But the second, each node starts and then fails.
On the log I have the following on all of them:
INFO [main] 2015-11-27 19:40:21,168 ColumnFamilyStore.java:381 -
Initializing sy
