Definitely B.
On Thu, Jan 21, 2016 at 11:42 AM Robert Coli wrote:
> On Thu, Jan 21, 2016 at 11:37 AM, Kevin Burton wrote:
>
>> I think there are two strategies to upgradesstables after a release.
>>
>> We're doing a 2.0 to 2.1 upgrade (been procrastinating here).
>>
>> I think we can go with B
On Thu, Jan 21, 2016 at 11:37 AM, Kevin Burton wrote:
> I think there are two strategies to upgradesstables after a release.
>
> We're doing a 2.0 to 2.1 upgrade (been procrastinating here).
>
> I think we can go with B below... Would you agree?
>
> Strategy A:
>
> - foreach server
>
I think there are two strategies to upgradesstables after a release.
We're doing a 2.0 to 2.1 upgrade (been procrastinating here).
I think we can go with B below... Would you agree?
Strategy A:
- foreach server
- upgrade to 2.1
- nodetool upgradesstables
Strategy B:
-
We are upgrading from DSE 3.2 (C*1.2) to 4.5(C*2.0.11) in 6 node cluster
with replication factor =3. App uses CL quorum.
Testing the rolling upgrade in 6 node cluster by upgrading one node at a
time. During the upgrade, we have test script that is tyring to simulate
prod load to write/read data
t;
>> ...
>
>> Two similar issues were reported, but without satisfactory responses:
>>
>> -
>> http://stackoverflow.com/questions/15355115/rolling-upgrade-for-cassandra-1-0-9-cluster-to-1-2-1
>> - https://issues.apache.org/jira/browse/CASSANDRA-5740
>>
>
> Bot
responses:
>
> -
> http://stackoverflow.com/questions/15355115/rolling-upgrade-for-cassandra-1-0-9-cluster-to-1-2-1
> - https://issues.apache.org/jira/browse/CASSANDRA-5740
>
Both of these issues relate to upgrading from 1._0_.x to 1.2.x, which is
not supported.
Were I you, I would su
if that's related to
the increased number read timeouts or just a coincidence. The timeout
configuration is the default (1ms).
Two similar issues were reported, but without satisfactory responses:
-
http://stackoverflow.com/questions/15355115/rolling-upgrade-for-cassandra-1-0-9-cluster-to-1-2
to roll upgrade from 1.0.12 to 1.2.5, but we found that the
> 1.2.5 node cannot see other old nodes.
> Therefore, we tried to upgrade to 1.1.12 first, and it works.
> However, we still saw the same issue when rolling upgrade from 1.1.12 to
> 1.2.5.
> This seems to be the fixed issue a
e other old nodes.
> Therefore, we tried to upgrade to 1.1.12 first, and it works.
> However, we still saw the same issue when rolling upgrade from 1.1.12 to
> 1.2.5.
> This seems to be the fixed issue as
> https://issues.apache.org/jira/browse/CASSANDRA-5332 but we still saw it
Hi,
We are trying to roll upgrade from 1.0.12 to 1.2.5, but we found that the
1.2.5 node cannot see other old nodes.
Therefore, we tried to upgrade to 1.1.12 first, and it works.
However, we still saw the same issue when rolling upgrade from 1.1.12 to
1.2.5.
This seems to be the fixed issue as
Thanks, I just pushed ahead with the rolling upgrade with bootstrap
off. This just meant the beta1 cluster got smaller and dissappeared
while the beta2 cluster got bigger and took over.
This is only a dev system so no writes will/should have been lost.
Ian
On 04/10/2010 14:55, Jonathan
from the Upgrading section of NEWS.txt:
The Cassandra inter-node protocol is incompatible with 0.6.x
releases (and with 0.7 beta1), meaning you will have to bring your
cluster down prior to upgrading
On Mon, Oct 4, 2010 at 8:53 AM, Ian Rogers wrote:
>
> I've tried to d
I've tried to do a rolling upgrade of a 3-node ring from beta1 to beta2
but got the error below. The new node seems to come up fine - I can
connect to it with cassandra-cli and see the keyspaces - but it doesn't
join the ring.
My method was:
- stop old cassandra
- mv old cassandra
Hi Gary,
Thanks for answering my question. I thought that could be a tough
question as Cassandra is quickly evolving recently, but it was great
to know that you guys are always trying to make rolling upgrade
possible for minor upgrades.
My friend is evaluating Cassandra as an HA
On Mon, May 10, 2010 at 17:01, Tatsuya Kawano wrote:
> Hi,
>
> Does Cassandra support rolling restart recipe between minor version
> upgrade? I mean rolling restart is a way to upgrade Cassandra version
> or change configuration **without** bringing down the whole cluster.
> The recipe will be som
Hi,
Does Cassandra support rolling restart recipe between minor version
upgrade? I mean rolling restart is a way to upgrade Cassandra version
or change configuration **without** bringing down the whole cluster.
The recipe will be something like killing a couple of nodes at a time
and starting them
16 matches
Mail list logo
