I guess also OS-level page cache also will help out implicitly to make sure
your common pages aren't touching disk.
On Fri, Sep 14, 2018 at 2:46 AM Alaa Zubaidi (PDF)
wrote:
> Hi,
>
> We are using Apache Cassandra 3.11.2 on RedHat 7
> The data can grow to +100TB however the hot data will be in
;
>
>
> Sean Durity
>
>
>
> *From:* DuyHai Doan
> *Sent:* Monday, September 17, 2018 4:23 PM
> *To:* user
> *Subject:* Re: [EXTERNAL] Re: cold vs hot data
>
>
>
> Sean
>
>
>
> Without transactions à la SQL, how can you guarantee atomicity betwee
Let me check lvmcache..Thanks
On Thu, Sep 13, 2018 at 11:39 PM, Mateusz
wrote:
> On piątek, 14 września 2018 02:46:43 CEST Alaa Zubaidi (PDF) wrote:
> > The data can grow to +100TB however the hot data will be in most cases
> less
> > than 10TB but we still need to keep the rest of data
Thanks Ben, I will try this on 4.0 when its available.
On Thu, Sep 13, 2018 at 7:06 PM, Ben Slater
wrote:
> Not quite a solution but you will probably be interested in the discussion
> on this ticket: https://issues.apache.org/jira/browse/CASSANDRA-8460
>
> On Fri, 14 Sep 2018 at 10:46 Alaa
Durity
From: DuyHai Doan
Sent: Monday, September 17, 2018 4:23 PM
To: user
Subject: Re: [EXTERNAL] Re: cold vs hot data
Sean
Without transactions à la SQL, how can you guarantee atomicity between both
tables for upserts ? I mean, one write could succeed with hot table and fail
for cold table
>>
>>
>> Sean Durity
>>
>>
>> -Original Message-----
>> From: Mateusz
>> Sent: Friday, September 14, 2018 2:40 AM
>> To: user@cassandra.apache.org
>> Subject: [EXTERNAL] Re: cold vs hot data
>>
>> On piątek, 14 września 2
---Original Message-
> From: Mateusz
> Sent: Friday, September 14, 2018 2:40 AM
> To: user@cassandra.apache.org
> Subject: [EXTERNAL] Re: cold vs hot data
>
> On piątek, 14 września 2018 02:46:43 CEST Alaa Zubaidi (PDF) wrote:
> > The data can grow to +100TB however the hot
Subject: [EXTERNAL] Re: cold vs hot data
On piątek, 14 września 2018 02:46:43 CEST Alaa Zubaidi (PDF) wrote:
> The data can grow to +100TB however the hot data will be in most cases
> less than 10TB but we still need to keep the rest of data accessible.
> Anyone has this proble
On piątek, 14 września 2018 02:46:43 CEST Alaa Zubaidi (PDF) wrote:
> The data can grow to +100TB however the hot data will be in most cases less
> than 10TB but we still need to keep the rest of data accessible.
> Anyone has this problem?
> What is the best way to make the cluster more efficient?
Not quite a solution but you will probably be interested in the discussion
on this ticket: https://issues.apache.org/jira/browse/CASSANDRA-8460
On Fri, 14 Sep 2018 at 10:46 Alaa Zubaidi (PDF)
wrote:
> Hi,
>
> We are using Apache Cassandra 3.11.2 on RedHat 7
> The data can grow to +100TB however
Hi,
We are using Apache Cassandra 3.11.2 on RedHat 7
The data can grow to +100TB however the hot data will be in most cases less
than 10TB but we still need to keep the rest of data accessible.
Anyone has this problem?
What is the best way to make the cluster more efficient?
Is there a way to
11 matches
Mail list logo