te:
>>
>> The only true drain is
>> 1) turn on ip tables to stop all incoming traffic
>> 2) flush
>> 3) wait
>> 4) delete files
>> 5) upgrade
>> 6) restart
>>
>>
>> On Thu, Jan 3, 2013 at 2:59 PM, Michael Kjellman > > wrote:
>&g
an
> wrote:
>
>> That's why I didn’t create a ticket as I knew there was one. But, I
>> thought this had been fixed in 1.1.7 ??
>>
>> From: Edward Capriolo
>> Reply-To: "user@cassandra.apache.org"
>> Date: Thursday, January 3, 2013 11:57 AM
>> To:
el Kjellman
> wrote:
> That's why I didn’t create a ticket as I knew there was one. But, I thought
> this had been fixed in 1.1.7 ??
>
> From: Edward Capriolo
> Reply-To: "user@cassandra.apache.org"
> Date: Thursday, January 3, 2013 11:57 AM
> To: "
ed in 1.1.7 ??
>
> From: Edward Capriolo
> Reply-To: "user@cassandra.apache.org"
> Date: Thursday, January 3, 2013 11:57 AM
> To: "user@cassandra.apache.org"
> Subject: Re: Error after 1.2.0 upgrade
>
> There is a bug on this, drain has been in a weird sta
gt;>
Date: Thursday, January 3, 2013 11:57 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Error after 1.2.0 upgrade
There is a bug on this, drain has been in a weird state for a long time. In 1.0
> cluster which I am slowly massaging into a good state I haven't seen this in
> 15+ hours of operation…
>
> This looks related to JNA?
>
> From: Alain RODRIGUEZ
> Reply-To: "user@cassandra.apache.org"
> Date: Thursday, January 3, 2013 8:42 AM
> To:
ug for that yet
>
> Best,
> Micahel
>
> From: Michael Kjellman
> Reply-To: "user@cassandra.apache.org"
> Date: Thursday, January 3, 2013 11:42 AM
> To: "user@cassandra.apache.org"
> Subject: Re: Error after 1.2.0 upgrade
>
> Trac
@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: Error after 1.2.0 upgrade
Tracking Issues:
https://issues.apache.org/jira/browse/CASSANDRA-5101
https://issues.apache.org/jira/browse/CASSANDRA-5104 which was created because
gt;>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Thursday, January 3, 2013 11:38 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
> Date: Thursday, January 3, 2013 8:42 AM
> To: "user@cassandra.apache.org"
> Subject: Error after 1.2.0 upgrade
>
> In a dev env, C* 1.1.7 -> 1.2.0, 1 node.
>
> I run Cassandra in a 8GB memory environment.
>
> The upgrade went well, but I sometimes have
in 15+ hours of operation…
>>
>> This looks related to JNA?
>>
>> From: Alain RODRIGUEZ
>> Reply-To: "user@cassandra.apache.org"
>> Date: Thursday, January 3, 2013 8:42 AM
>> To: "user@cassandra.apache.org"
>> Subject: Error after 1.2.0 upgrade
&g
ration…
This looks related to JNA?
From: Alain RODRIGUEZ mailto:arodr...@gmail.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Thursday, January 3, 2013 8:42 AM
To: "user@cassandra.apache.org&l
issues from 1.1.7 -> 1.2.0 atm but in a 12 node
> cluster which I am slowly massaging into a good state I haven't seen this
> in 15+ hours of operation…
>
> This looks related to JNA?
>
> From: Alain RODRIGUEZ
> Reply-To: "user@cassandra.apache.org"
> Dat
ser@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Thursday, January 3, 2013 8:42 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Error after 1.2.0 upg
14 matches
Mail list logo
