Re: Hints folder missing in Cassandra

Hi, There are no piece of code in Cassandra that would remove this folder. You should start looking elsewhere, like other people mentioned (chef, ansible and so on), good luck On 8 February 2018 at 22:54, test user wrote: > Does anyone have more inputs on the missing hints

GDPR, Right to Be Forgotten, and Cassandra

Hi everyone, Because of GDPR we really face the need to support “Right to Be Forgotten” requests => https://gdpr-info.eu/art-17-gdpr/ stating that *"the controller shall have the obligation to erase personal data without undue delay"* Because I usually meet customers that do not have that much

Re: GDPR, Right to Be Forgotten, and Cassandra

I think you're introducing a layer violation. GDPR is a business requirement and compaction is an implementation detail. IMHO it's enough to delete the partition using regular CQL. It's true that it won't be deleted immedietly but it will be eventually deleted (welcome to eventual consistency ;).

Re: GDPR, Right to Be Forgotten, and Cassandra

The times I have run into similar requirements from legislation or standards the fact that SELECT no longer returns the data is enough for all auditors I have worked with. Otherwise you get down into screwy requirements of needing to zero out all unused sectors on your disks to actually remove

Re: GDPR, Right to Be Forgotten, and Cassandra

Or use the new user-defined compaction option recently introduced, provided you can determine over which SSTables a partition is spread On Fri, Feb 9, 2018 at 5:23 PM, Jon Haddad wrote: > Give this a read through: > >

Re: GDPR, Right to Be Forgotten, and Cassandra

Give this a read through: https://github.com/protectwise/cassandra-util/tree/master/deleting-compaction-strategy Basically you write your own logic for how stuff gets forgotten, then you can recompact

Re: GDPR, Right to Be Forgotten, and Cassandra

That might be fine for a one off but is totally impractical at scale or when using TWCS. On Fri, Feb 9, 2018 at 8:39 AM DuyHai Doan wrote: > Or use the new user-defined compaction option recently introduced, > provided you can determine over which SSTables a partition is

Re: LWT broken?

In this case, we only write using CAS (code guarantees that). We also never update, just insert if not exist. Once a hash exists, it never changes (it may get deleted later and that'll be a CAS delete as well). -- Mahdi. On 2/9/18 1:38 PM, Jeff Jirsa wrote: On Fri, Feb 9, 2018 at 1:33 PM,

Re: LWT broken?

I'd not recommend using any consistency level but serial for reading tables updated by LWT operations. Otherwise you might end up reading inconsistent results. On 09.02.18 08:06, Mahdi Ben Hamida wrote: > > Hello, > > I'm running a 2.0.17 cluster (I know, I know, need to upgrade) with 46 > nodes

Re: LWT broken?

If you want consistent reads you have to use the CL that enforces it. There’s no way around it. On Fri, Feb 9, 2018 at 2:35 PM Mahdi Ben Hamida wrote: > In this case, we only write using CAS (code guarantees that). We also > never update, just insert if not exist. Once a hash

Re: GDPR, Right to Be Forgotten, and Cassandra

Deleting data "without undue delay" in Cassandra can be implemented by using crypto shredding and pseudonymization strategies in your data model. All you have to do is to make sure that throwing away a person's data encryption key will make it impossible to restore personal data and impossible to

Re: LWT broken?

Hi Stefan, I was hoping we could avoid the cost of a serial read (which I assume is a lot more expensive than a regular read due to the paxos requirements). I actually do a serial read at line #9 (ie, when we lose the LWT and have to read the winning value) and that still fails to ensure the

Re: LWT broken?

On Fri, Feb 9, 2018 at 1:33 PM, Mahdi Ben Hamida wrote: > Under what circumstances would we be reading inconsistent results ? Is > there a case where we end up reading a value that actually end up not being > written ? > > > If you ever write the same value with CAS and

Re: What kind of Automation you have for Cassandra related operations on AWS ?

On Fri, Feb 9, 2018 at 12:46 AM, Krish Donald wrote: > Hi All, > > What kind of Automation you have for Cassandra related operations on AWS > like restacking, restart of the cluster , changing cassandra.yaml > parameters etc ? > We wrote some scripts customized for

Re: Bootstrapping fails with < 128GB RAM ...

Hi Jon, should I register to the JIRA and open an Issue or will you do so? I'm currently trying to bootstrap another node - with 100GB RAM, this time, and I'm recording Java Heap Memory over time via Jconsole, Top Threads and do monitoring the debug.log. There, in the debug.log, I can see, that

Re: Refresh from Prod to Dev

If you have equivalent number of nodes then use snapshot to backup and then restore them on Dev. You will need to create the schema on the Dev box. The CFiD will be different so at most you may have to rename the Prod sstable dirs to match whats on Dev. Another method is to use sstableloader

Re: Refresh from Prod to Dev

Hi Anshu, We used to have similar requirements in my workplace. We tried multiple options like snapshot and restore it but the best one which worked for us was making a same number of nodes of cas cluster in preprod and doing a parallel scp of the data directly from production to preprod and

Re: What kind of Automation you have for Cassandra related operations on AWS ?

Working on a Kubernetes operator for Cassandra (Alpha stage...) Le 9 févr. 2018 12:56 PM, "Oleksandr Shulgin" a écrit : > On Fri, Feb 9, 2018 at 12:46 AM, Krish Donald > wrote: > >> Hi All, >> >> What kind of Automation you have for Cassandra

Re: What kind of Automation you have for Cassandra related operations on AWS ?

On Fri, Feb 9, 2018 at 1:01 PM, vincent gromakowski < vincent.gromakow...@gmail.com> wrote: > Working on a Kubernetes operator for Cassandra (Alpha stage...) > I would love to learn more about your approach. Do you have anything to show already? Design docs / prototype? -- Alex

Re: What kind of Automation you have for Cassandra related operations on AWS ?

It will clearly follow your colleagues approach on the postgresql operator https://github.com/zalando-incubator/postgres-operator Just watch my repo for a first beta working version in the next weeks https://github.com/vgkowski/cassandra-operator 2018-02-09 15:20 GMT+01:00 Oleksandr Shulgin