s mostly overwrites
>> Be heavily trafficked
>> Using the in-memory option | DataStax Enterprise 4.0 Documentation
>>
>>
>>
>>
>>
>>
>> Using the in-memory option | DataStax Enterprise 4.0 Documentation
>> Using the in-me
gt;
>
>
>
>
>
> Using the in-memory option | DataStax Enterprise 4.0 Documentation
> Using the in-memory option
> View on www.datastax.com
> Preview by Yahoo
>
>
>
> hope this helps
> Jan
>
> C* Architect
>
>
>
> On Sunda
Hi guys,
Please, does anyone here already mounted a specific keyspace directory to
ram memory using tmpfs?
Do you see any problem doing so, except by the fact that the data can be
lost?
Thanks in advance.
Regards,
Gabriel.
tasks such as compaction, and we really struggled to
> successfully bootstrap or repair in that DC (2.1.1 cluster).
>> On Sun Nov 16 2014 at 6:49:31 AM Gabriel Menegatti
>> wrote:
>> Hello,
>>
>> We are using Cassandra 2.1.2 in a multi dc cluster (30 servers on DC1
Hello,
We are using Cassandra 2.1.2 in a multi dc cluster (30 servers on DC1 and
10 on DC2) with a key space replication factor of 1 on DC1 and 2 on DC2.
For some reason when we increase the volume of write requests on DC1 (using
ONE or LOCAL_ONE), the Cassandra java process on DC2 nodes goes dow