ins the property of the sender. You must not use,
>>> disclose, distribute, copy, print or rely on this e-mail. If you have
>>> received this message in error, please contact the sender immediately and
>>> irrevocably delete this message and any copies.
>>>
>>
eived this message in error, please contact the sender immediately and
>> irrevocably delete this message and any copies.
>>
>> *From:* Rene Kochen [mailto:rene.koc...@emea.schange.com]
>> *Sent:* Monday, September 10, 2012 14:47
>> *To:* user@cassandra.apache.org
>> *Subject:* R
y, September 10, 2012 17:03
To: user@cassandra.apache.org
Subject: Re: High commit size
For performance reasons I switched to memory mapped IO. Is there a way to make
memory-mapped IO work in Windows?
Thanks!
2012/9/10 Viktor Jevdokimov
mailto:viktor.jevdoki...@adform.com>>
Do not use mmap/a
ne.koc...@emea.schange.com]
> *Sent:* Monday, September 10, 2012 14:47
> *To:* user@cassandra.apache.org
> *Subject:* Re: High commit size
>
> ** **
>
> The problem is that the system just freezes and nodes are dying. The
> system becomes very unresponsive and it always
emea.schange.com]
Sent: Monday, September 10, 2012 14:47
To: user@cassandra.apache.org
Subject: Re: High commit size
The problem is that the system just freezes and nodes are dying. The system
becomes very unresponsive and it always happens when the shareable amount of
RAM reaches the total numb
The problem is that the system just freezes and nodes are dying. The system
becomes very unresponsive and it always happens when the shareable amount
of RAM reaches the total number of bytes in the system.
Is there something in Windows that I can tune in order to avoid this
behavior? I cannot easi
It is memory-mapped I/O. I wouldn't worry about it.
BTW, Windows might not be the best choice to run Cassandra on. My
experience running Cassandra on Windows has not been positive one. We
no longer support Windows as our production platform.
Regards,
Oleg
On 2012-09-10 09:00:02 +, Rene
