Re: Compaction Strategy

[Nitan Kainth]

It’s not recommended to disable compaction, you will end up with hundreds to 
thousands of sstables and increased read latency. If your data is immitable, 
means no update/deletes it will have least impact.

Decreasing compaction throughput will release resources for application but 
don’t accumulate too many pending compaction tasks.

Sent from my iPhone

> On Sep 19, 2018, at 4:44 PM, rajasekhar kommineni  wrote:
> 
> Hello,
> 
> Can any one respond to my questions. Is it a good idea to disable auto 
> compaction and schedule it every 3 days. I am unable to control compaction 
> and it is causing timeouts. 
> 
> Also will reducing or increasing compaction_throughput_mb_per_sec eliminate 
> timeouts ?
> 
> Thanks,
> 
> 
>> On Sep 17, 2018, at 9:38 PM, rajasekhar kommineni  
>> wrote:
>> 
>> Hello Folks,
>> 
>> I need advice in deciding the compaction strategy for my C cluster. There 
>> are multiple jobs that will load the data with less inserts and more updates 
>> but no deletes. Currently I am using Size Tired compaction, but seeing auto 
>> compactions after the data load kicks, and also read timeouts during 
>> compaction.
>> 
>> Can anyone suggest good compaction strategy for my cluster which will reduce 
>> the timeouts.
>> 
>> 
>> Thanks,
>> 
> 
> 
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
> 

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: [EXTERNAL] Re: cold vs hot data

[Alaa Zubaidi (PDF)]

This is one of the options that we are thinking of, but this will require
more storage, which is something that we are trying to avoid.
We will test the performance for the batch inserts.
Thanks

On Tue, Sep 18, 2018 at 6:35 AM, Durity, Sean R  wrote:

> Wouldn’t you have the same problem with two similar tables with different
> primary keys (eg., UserByID and UserByName)? This is a very common pattern
> in Cassandra – inserting into multiple tables… That’s what batches are for
> – atomicity.
>
> I don’t understand the additional concern here.
>
>
>
>
>
>
>
> 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 between
> both tables for upserts ? I mean, one write could succeed with hot table
> and fail for cold table
>
>
>
> The only solution I see is using logged batch, with a huge overhead and
> perf hit on for the writes
>
>
>
> On Mon, Sep 17, 2018 at 8:28 PM, Durity, Sean R <
> sean_r_dur...@homedepot.com> wrote:
>
> An idea:
>
> On initial insert, insert into 2 tables:
> Hot with short TTL
> Cold/archive with a longer (or no) TTL
> Then your hot data is always in the same table, but being expired. And you
> can access the archive table only for the more rare circumstances. Then you
> could have the HOT table on a different volume of faster storage. If the
> hot/cold tables are in different keyspaces, then you could also have
> different replication (a HOT DC and an archive DC, for example)
>
>
> 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 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?
> > Is there a way to somehow automatically move the old data to different
> > storage (rack, dc, etc)?
> > Any ideas?
>
> We solved it using lvmcache.
>
> --
> Mateusz
> (...) mam brata - poważny, domator, liczykrupa, hipokryta, pobożniś,
> krótko mówiąc - podpora społeczeństwa."
> Nikos Kazantzakis - "Grek Zorba"
>
>
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
> 
>
> The information in this Internet Email is confidential and may be legally
> privileged. It is intended solely for the addressee. Access to this Email
> by anyone else is unauthorized. If you are not the intended recipient, any
> disclosure, copying, distribution or any action taken or omitted to be
> taken in reliance on it, is prohibited and may be unlawful. When addressed
> to our clients any opinions or advice contained in this Email are subject
> to the terms and conditions expressed in any applicable governing The Home
> Depot terms of business or client engagement letter. The Home Depot
> disclaims all responsibility and liability for the accuracy and content of
> this attachment and for any damages or losses arising from any
> inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other
> items of a destructive nature, which may be contained in this attachment
> and shall not be liable for direct, indirect, consequential or special
> damages in connection with this e-mail message or its attachment.
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>
>
> --
>
> The information in this Internet Email is confidential and may be legally
> privileged. It is intended solely for the addressee. Access to this Email
> by anyone else is unauthorized. If you are not the intended recipient, any
> disclosure, copying, distribution or any action taken or omitted to be
> taken in reliance on it, is prohibited and may be unlawful. When addressed
> to our clients any opinions or advice contained in this Email are subject
> to the terms and conditions expressed in any applicable governing The Home
> Depot terms of business or client engagement letter. The Home Depot
> disclaims all responsibility and liability for the accuracy and content of
> this attachment and for any damages or losses arising from any
> inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other
> items of a destructive nature, which may be contained in this attachment
> and shall not be liable for direct, indirect, consequential or special
> damages in connection with this e-mail message or its attachment.
>



-- 

Alaa 

Re: cold vs hot data

[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 accessible.
> > Anyone has this problem?
> > What is the best way to make the cluster more efficient?
> > Is there a way to somehow automatically move the old data to different
> > storage (rack, dc, etc)?
> > Any ideas?
>
> We solved it using lvmcache.
>
> --
> Mateusz
> (...) mam brata - poważny, domator, liczykrupa, hipokryta, pobożniś,
> krótko mówiąc - podpora społeczeństwa."
> Nikos Kazantzakis - "Grek Zorba"
>
>
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>


-- 

Alaa Zubaidi
PDF Solutions, Inc.
333 West San Carlos Street, Suite 1000
San Jose, CA 95110  USA
Tel: 408-283-5639
fax: 408-938-6479
email: alaa.zuba...@pdf.com

-- 
This message may contain confidential and privileged information. If it has 
been sent to you in error, please reply to advise the sender of the error 
and then immediately permanently delete it and all attachments to it from 
your systems. If you are not the intended recipient, do not read, copy, 
disclose or otherwise use this message or any attachments to it. The sender 
disclaims any liability for such unauthorized use.  PLEASE NOTE that all 
incoming e-mails sent to PDF e-mail accounts will be archived and may be 
scanned by us and/or by external service providers to detect and prevent 
threats to our systems, investigate illegal or inappropriate behavior, 
and/or eliminate unsolicited promotional e-mails (“spam”).  If you have any 
concerns about this process, please contact us at legal.departm...@pdf.com 
.

Re: Cassandra system table diagram

[Joseph Arriola]

Hi, I recomend this

http://kdm.dataview.org/

its free and it has the implementation of good design practices that you
can find in the DataStax courses.




2018-09-19 11:26 GMT-06:00 Abdul Patel :

> Hi,
>
> Do we have somehwere cassandra system tables relation diagram?
> Or just system table diagram?
>

Re: cold vs hot data

[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 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 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 somehow automatically move the old data to different
>> storage (rack, dc, etc)?
>> Any ideas?
>>
>> Regards,
>>
>> --
>>
>> Alaa
>>
>>
>> *This message may contain confidential and privileged information. If it
>> has been sent to you in error, please reply to advise the sender of the
>> error and then immediately permanently delete it and all attachments to it
>> from your systems. If you are not the intended recipient, do not read,
>> copy, disclose or otherwise use this message or any attachments to it. The
>> sender disclaims any liability for such unauthorized use. PLEASE NOTE that
>> all incoming e-mails sent to PDF e-mail accounts will be archived and may
>> be scanned by us and/or by external service providers to detect and prevent
>> threats to our systems, investigate illegal or inappropriate behavior,
>> and/or eliminate unsolicited promotional e-mails (“spam”). If you have any
>> concerns about this process, please contact us at *
>> *legal.departm...@pdf.com* *.*
>
> --
>
>
> *Ben Slater*
>
> *Chief Product Officer *
>
>    
>
>
> Read our latest technical blog posts here
> .
>
> This email has been sent on behalf of Instaclustr Pty. Limited (Australia)
> and Instaclustr Inc (USA).
>
> This email and any attachments may contain confidential and legally
> privileged information.  If you are not the intended recipient, do not copy
> or disclose its content, but please reply to this email immediately and
> highlight the error to the sender and then immediately delete the message.
>



-- 

Alaa Zubaidi
PDF Solutions, Inc.
333 West San Carlos Street, Suite 1000
San Jose, CA 95110  USA
Tel: 408-283-5639
fax: 408-938-6479
email: alaa.zuba...@pdf.com

-- 
This message may contain confidential and privileged information. If it has 
been sent to you in error, please reply to advise the sender of the error 
and then immediately permanently delete it and all attachments to it from 
your systems. If you are not the intended recipient, do not read, copy, 
disclose or otherwise use this message or any attachments to it. The sender 
disclaims any liability for such unauthorized use.  PLEASE NOTE that all 
incoming e-mails sent to PDF e-mail accounts will be archived and may be 
scanned by us and/or by external service providers to detect and prevent 
threats to our systems, investigate illegal or inappropriate behavior, 
and/or eliminate unsolicited promotional e-mails (“spam”).  If you have any 
concerns about this process, please contact us at legal.departm...@pdf.com 
.

Re: Compaction Strategy

[rajasekhar kommineni]

Hello,

Can any one respond to my questions. Is it a good idea to disable auto 
compaction and schedule it every 3 days. I am unable to control compaction and 
it is causing timeouts. 

Also will reducing or increasing compaction_throughput_mb_per_sec eliminate 
timeouts ?

Thanks,


> On Sep 17, 2018, at 9:38 PM, rajasekhar kommineni  wrote:
> 
> Hello Folks,
> 
> I need advice in deciding the compaction strategy for my C cluster. There are 
> multiple jobs that will load the data with less inserts and more updates but 
> no deletes. Currently I am using Size Tired compaction, but seeing auto 
> compactions after the data load kicks, and also read timeouts during 
> compaction.
> 
> Can anyone suggest good compaction strategy for my cluster which will reduce 
> the timeouts.
> 
> 
> Thanks,
> 


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Cassandra system table diagram

[Abdul Patel]

Hi,

Do we have somehwere cassandra system tables relation diagram?
Or just system table diagram?

Re: Error during truncate: Cannot achieve consistency level ALL , how to fix it

[sha p]

RF is replication factor. Sorry for confusing

On 19 Sep 2018 5:45 p.m., "Jonathan Baynes" 
wrote:

What RF is your system_auth keyspace?



If its one, match it to the user keyspace, and restart the node.



*From:* sha p [mailto:shatestt...@gmail.com]
*Sent:* 19 September 2018 11:49
*To:* user@cassandra.apache.org
*Subject:* Error during truncate: Cannot achieve consistency level ALL ,
how to fix it



Hi All,

 I am new to Cassandra. Following below link



https://grokonez.com/spring-framework/spring-data/start-spring-data-cassandra-springboot#III_Sourcecode






I have three node cluster , keyspace set with RF = 2 , but when I run this
application from above source code bellow error is thrown

 Caused by: com.datastax.driver.core.exceptions.TruncateException: Error
during truncate: Cannot achieve consistency level ALL """ 





What wrong i am doing here ..How to fix it ? Plz help me.



Regards,

Shyam



This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy it. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is
strictly forbidden. Tradeweb reserves the right to monitor all e-mail
communications through its networks. If you do not wish to receive
marketing emails about our products / services, please let us know by
contacting us, either by email at contac...@tradeweb.com or by writing to
us at the registered office of Tradeweb in the UK, which is: Tradeweb
Europe Limited (company number 3912826), 1 Fore Street Avenue London EC2Y
9DT. To see our privacy policy, visit our website @ www.tradeweb.com.

RE: Error during truncate: Cannot achieve consistency level ALL , how to fix it

[Jonathan Baynes]

What RF is your system_auth keyspace?

If its one, match it to the user keyspace, and restart the node.

From: sha p [mailto:shatestt...@gmail.com]
Sent: 19 September 2018 11:49
To: user@cassandra.apache.org
Subject: Error during truncate: Cannot achieve consistency level ALL , how to 
fix it

Hi All,
 I am new to Cassandra. Following below link

https://grokonez.com/spring-framework/spring-data/start-spring-data-cassandra-springboot#III_Sourcecode


I have three node cluster , keyspace set with RF = 2 , but when I run this 
application from above source code bellow error is thrown
 Caused by: com.datastax.driver.core.exceptions.TruncateException: Error during 
truncate: Cannot achieve consistency level ALL """ 


What wrong i am doing here ..How to fix it ? Plz help me.

Regards,
Shyam



This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy it. Any unauthorized copying, 
disclosure or distribution of the material in this e-mail is strictly 
forbidden. Tradeweb reserves the right to monitor all e-mail communications 
through its networks. If you do not wish to receive marketing emails about our 
products / services, please let us know by contacting us, either by email at 
contac...@tradeweb.com or by writing to us at the registered office of Tradeweb 
in the UK, which is: Tradeweb Europe Limited (company number 3912826), 1 Fore 
Street Avenue London EC2Y 9DT. To see our privacy policy, visit our website @ 
www.tradeweb.com.

Cassandra repair in different version

[nokia ceph]

Hi ,

i have 5 node cassandra cluster. 3 nodes are in 3.0.13 version and 2 nodes
are in 3.0.6.
Is it safe to do a node repair on the cluster??

 Regards,
Renoy

Error during truncate: Cannot achieve consistency level ALL , how to fix it

[sha p]

>
> Hi All,
>>>  I am new to Cassandra. Following below link
>>>
>>>
>>> https://grokonez.com/spring-framework/spring-data/start-spring-data-cassandra-springboot#III_Sourcecode
>>>
>>>
>>> I have three node cluster , keyspace set with RF = 2 , but when I run
>>> this application from above source code bellow error is thrown
>>>  Caused by: com.datastax.driver.core.exceptions.TruncateException: Error
>>> during truncate: Cannot achieve consistency level ALL """ 
>>>
>>>
>>> What wrong i am doing here ..How to fix it ? Plz help me.
>>>
>>> Regards,
>>> Shyam
>>>
>>