The last patch on that ticket is what we're running in prod. Its
working well for us with disk_failure_mode: readwrite. In the case of
filesystem errors the node shuts off thrift and gossip. While the
gossip is propagating we can continue to serve some reads out of the
caches.
-ryan
On Tue, Aug 2
On Mon, Aug 1, 2011 at 6:12 PM, Ryan King wrote:
> On Fri, Jul 29, 2011 at 12:02 PM, Chris Burroughs
> wrote:
>> On 07/25/2011 01:53 PM, Ryan King wrote:
>>> Actually I was wrong– our patch will disable gosisp and thrift but
>>> leave the process running:
>>>
>>> https://issues.apache.org/jira/br
On Fri, Jul 29, 2011 at 12:02 PM, Chris Burroughs
wrote:
> On 07/25/2011 01:53 PM, Ryan King wrote:
>> Actually I was wrong– our patch will disable gosisp and thrift but
>> leave the process running:
>>
>> https://issues.apache.org/jira/browse/CASSANDRA-2118
>>
>> If people are interested in that
On 07/25/2011 01:53 PM, Ryan King wrote:
> Actually I was wrong– our patch will disable gosisp and thrift but
> leave the process running:
>
> https://issues.apache.org/jira/browse/CASSANDRA-2118
>
> If people are interested in that I can make sure its up to date with
> our latest version.
Thank
disk full
>
>
> Does CASSANDRA-809 resolved or any other path can resolve the problem? Is
> there any way to avoid reboot the cassandra server?
> Thanks!
>
> Best Regards
> Donna li
>
> -邮件原件-
> 发件人: Jonathan Ellis [mailto:jbel...@gmail.com]
> 发送时间:
Actually I was wrong– our patch will disable gosisp and thrift but
leave the process running:
https://issues.apache.org/jira/browse/CASSANDRA-2118
If people are interested in that I can make sure its up to date with
our latest version.
-ryan
On Mon, Jul 25, 2011 at 10:07 AM, Ryan King wrote:
>
We have a patch somewhere that will kill the node on IOErrors, since
those tend to be of the class that are unrecoverable.
-ryan
On Thu, Jul 7, 2011 at 8:02 PM, Jonathan Ellis wrote:
> Yeah, ideally it should probably die or drop into read-only mode if it
> runs out of space.
> (https://issues.a
Yeah, ideally it should probably die or drop into read-only mode if it
runs out of space.
(https://issues.apache.org/jira/browse/CASSANDRA-809)
Unfortunately dealing with disk-full conditions tends to be a low
priority for many people because it's relatively easy to avoid with
decent monitoring, b
