Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9E8EF10A52 for ; Wed, 31 Dec 2014 03:24:14 +0000 (UTC) Received: (qmail 54774 invoked by uid 500); 31 Dec 2014 03:24:08 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 54722 invoked by uid 500); 31 Dec 2014 03:24:08 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 54702 invoked by uid 99); 31 Dec 2014 03:24:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Dec 2014 03:24:08 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lijianqi@jd.com designates 58.83.206.59 as permitted sender) Received: from [58.83.206.59] (HELO smtp.jd.com) (58.83.206.59) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Dec 2014 03:24:01 +0000 Received: from YYXXLIJIANQIPC (103.16.127.8) by HUB02.360buyAD.local (172.17.27.16) with Microsoft SMTP Server id 14.2.247.3; Wed, 31 Dec 2014 11:22:45 +0800 From: =?UTF-8?B?5p2O5bu65aWH?= To: References: In-Reply-To: Subject: =?UTF-8?Q?=E7=AD=94=E5=A4=8D:_Downgrade_from_2.1.2_to_2.1.?= =?UTF-8?Q?1?= Date: Wed, 31 Dec 2014 11:22:45 +0800 Message-ID: <058401d024a9$0ba2b570$22e82050$@jd.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0585_01D024EC.19C950D0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQDod1LLCBAfMRRiMBYykQ+KBo5BJgItkRMMAfqVC1ueVx/QsA== Content-Language: zh-cn X-Originating-IP: [103.16.127.8] X-Virus-Checked: Checked by ClamAV on apache.org ------=_NextPart_000_0585_01D024EC.19C950D0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable We also suffer some problem from 2.1.2 . But I think we can deal with .=20 First I don=E2=80=99t use incremental repair.=20 Second we restart node after repair . It will release sstable tmplink . Third , don=E2=80=99t use stop COMPACTION command. =20 If we read 2.1.2 release notes ,we find it solve some issues with 2.1.1 = .=20 We wait for 2.1.3 . =20 =20 _____ =20 =E6=9D=8E=E5=BB=BA=E5=A5=87 =E4=BA=AC=E4=B8=9C=E5=95=86=E5=9F=8E =E3=80=90 = =E8=BF=90=E8=90=A5=E7=A0=94=E5=8F=91 = =E6=9E=B6=E6=9E=84=E5=B8=88=E3=80=91 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =E6=89=8B=E6=9C=BA=EF=BC=9A18600360358 =E5=9C=B0=E5=9D=80=EF=BC=9A=E5=8C=97=E4=BA=AC=E5=B8=82=E5=A4=A7=E5=85=B4=E5= =8C=BA =E6=9C=9D=E6=9E=97=E5=B9=BF=E5=9C=BA25=E5=B1=82 =E9=82=AE=E7=BC=96=EF=BC=9A100101 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =E7=BD=91=E8=B4=AD=E4=B8=8A=E4=BA=AC=E4=B8=9C=EF=BC=8C=E7=9C=81=E9=92=B1=E5= =8F=88=E6=94=BE=E5=BF=83=EF=BC=81 www.jd.com =20 =20 =E5=8F=91=E4=BB=B6=E4=BA=BA: Phil Burress = [mailto:philtburress@gmail.com]=20 =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: = 2014=E5=B9=B412=E6=9C=8831=E6=97=A5 2:53 =E6=94=B6=E4=BB=B6=E4=BA=BA: user@cassandra.apache.org =E4=B8=BB=E9=A2=98: Re: Downgrade from 2.1.2 to 2.1.1 =20 Thanks Rob. =20 On Tue, Dec 30, 2014 at 1:38 PM, Robert Coli = wrote: On Tue, Dec 30, 2014 at 9:42 AM, Phil Burress = wrote: We are having a lot of problems with release 2.1.2. It was suggested = here we should downgrade to 2.1.1 if possible.=20 =20 For the experts out there, do you foresee any issues in doing this? =20 Not sure if advice from the person who suggested the downgrade is what = you're looking for, but... =20 The classes of risk are : =20 - Incompatible changes to system keyspace values (unlikely, but possible = in a minor version) - File format changes (very unlikely in a minor version) - Network protocol changes (very unlikely in a minor version) - Unexpected exceptions of other classes (monitor in logs) =20 Really, read the CHANGES.txt for 2.1.2 and look for the above classes of = risk. If you have any questions about specific tickets, feel free to ask = on-thread? =20 It's also worth pointing out that you can just downgrade a single node = and see if it still works. If it does, and doesn't except, you're = probably fine? =20 =3DRob PS - Pro-forma disclaimer that downgrading is officially unsupported. =20 ------=_NextPart_000_0585_01D024EC.19C950D0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

We also suffer some problem from 2.1.2 . But I think we can deal with = .

First I don=E2=80=99t use incremental repair. =

Second =C2=A0we restart node after repair . It will release sstable = tmplink .

Third , don=E2=80=99t use stop COMPACTION = command.

 

If we read 2.1.2 release notes ,we find it solve some issues with = 2.1.1 .

We wait for 2.1.3 .

 

 

=E6=9D=8E=E5=BB=BA=E5=A5=87

=E4=BA=AC=E4=B8=9C=E5=95=86=E5=9F=8E = =E3=80=90 =E8=BF=90=E8=90=A5=E7=A0=94=E5=8F=91 =E6=9E=B6=E6=9E=84=E5=B8=88=E3=80=91

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

=E6=89=8B=E6=9C=BA=EF=BC=9A18600360358

=E5=9C=B0=E5=9D=80=EF=BC=9A=E5=8C=97=E4=BA=AC= =E5=B8=82=E5=A4=A7=E5=85=B4=E5=8C=BA = =E6=9C=9D=E6=9E=97=E5=B9=BF=E5=9C=BA25=E5=B1=82

=E9=82=AE=E7=BC=96=EF=BC=9A100101

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

=E7=BD=91=E8=B4=AD=E4=B8=8A=E4=BA=AC=E4=B8=9C= =EF=BC=8C=E7=9C=81=E9=92=B1=E5=8F=88=E6=94=BE=E5=BF=83=EF=BC=81

www.jd.com

 

=E5=8F=91=E4=BB=B6=E4=BA=BA: Phil Burress [mailto:philtburress@gmail.com] =
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2014=E5=B9=B412=E6=9C=8831=E6=97=A5 = 2:53
=E6=94=B6=E4=BB=B6=E4=BA=BA: = user@cassandra.apache.org
=E4=B8=BB=E9=A2=98: Re: Downgrade from 2.1.2 to = 2.1.1

 

Thanks Rob.

 

On Tue, Dec 30, 2014 at 1:38 PM, = Robert Coli <rcoli@eventbrite.com> = wrote:

On Tue, Dec 30, 2014 at 9:42 AM, Phil Burress <philtburress@gmail.com> = wrote:

We are having a lot of problems with release 2.1.2. It was = suggested here we should downgrade to 2.1.1 if = possible. 

 

For the experts out there, do you = foresee any issues in doing = this?

 

Not sure if advice from the person = who suggested the downgrade is what you're looking for, = but...

 

The classes of risk are = :

 

- Incompatible changes to system = keyspace values (unlikely, but possible in a minor = version)

- File format changes (very unlikely in a minor = version)

- Network protocol changes (very unlikely in a minor = version)

- Unexpected exceptions of other classes (monitor in = logs)

 

Really, read the CHANGES.txt for = 2.1.2 and look for the above classes of risk. If you have any questions = about specific tickets, feel free to ask = on-thread?

 

It's also worth pointing out that = you can just downgrade a single node and see if it still works. If it = does, and doesn't except, you're probably = fine?

 

=3DRob

PS - Pro-forma disclaimer that = downgrading is officially = unsupported.

 

------=_NextPart_000_0585_01D024EC.19C950D0--