Re: cold vs hot data

2018-09-20 Thread Jens Rantil
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

Re: [EXTERNAL] Re: cold vs hot data

2018-09-19 Thread Alaa Zubaidi (PDF)
; > > > 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

Re: cold vs hot data

2018-09-19 Thread Alaa Zubaidi (PDF)
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

Re: cold vs hot data

2018-09-19 Thread Alaa Zubaidi (PDF)
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

RE: [EXTERNAL] Re: cold vs hot data

2018-09-18 Thread Durity, Sean R
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

Re: [EXTERNAL] Re: cold vs hot data

2018-09-17 Thread DuyHai Doan
>> >> >> 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

Re: [EXTERNAL] Re: cold vs hot data

2018-09-17 Thread DuyHai Doan
---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

RE: [EXTERNAL] Re: cold vs hot data

2018-09-17 Thread Durity, Sean R
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

Re: cold vs hot data

2018-09-14 Thread Mateusz
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?

Re: cold vs hot data

2018-09-13 Thread Ben Slater
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

cold vs hot data

2018-09-13 Thread Alaa Zubaidi (PDF)
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