Hello,
I'm running a 2.0.17 cluster (I know, I know, need to upgrade) with 46
nodes across 3 racks (& RF=3). I'm seeing that under high contention,
LWT may actually not guarantee uniqueness. With a total of 16 million
LWT transactions (with peak LWT concurrency around 5k/sec), I found 38
conf
Team ,
I want to validate and POC on production data. Data on production is huge.
What could be optimal method to move the data from Prod to Dev
environment? I know there are few solutions but what/which is most
efficient method do refresh for dev env?
--
*C*heers,*
*Anshu V*
Terraform, Packer and Ansible does pretty decently, you may have to do some
smarts around replacing nodes and attaching the right volumes to replaced
nodes. If you could get Kubernetes working with Cassandra (beyond the
readily available guides) then I think you'll be a total baller.
On 9 February
Terraform plus ansible. Put ok but messy. 5-30,000 nodes and infra
Daemeon (Dæmœn) Reiydelle
USA 1.415.501.0198
On Thu, Feb 8, 2018, 15:57 Ben Wood wrote:
> Shameless plug of our (DC/OS) Apache Cassandra service:
> https://docs.mesosphere.com/services/cassandra/2.0.3-3.0.14.
>
> You must run D
At Teads we use Terraform, Chef, Packer and Rundeck for our AWS infrastructure.
I'll publish a blog post on Medium which talk about that, it's in the pipeline.
Terraform is awesome.
Best,
RomainLe vendredi 9 février 2018 à 00:57:01 UTC+1, Ben Wood
a écrit :
Shameless plug of our (DC/
Shameless plug of our (DC/OS) Apache Cassandra service:
https://docs.mesosphere.com/services/cassandra/2.0.3-3.0.14.
You must run DC/OS, but it will handle:
Restarts
Replacement of nodes
Modification of configuration
Backups and Restores (to S3)
On Thu, Feb 8, 2018 at 3:46 PM, 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 ?
Thanks
Does anyone have more inputs on the missing hints folder, rather why it
gets deleted.
Has anyone run into this scenario before?
Regards,
Cassandra User
On Wed, Feb 7, 2018 at 9:21 PM, test user wrote:
> The problem is even though, I get that O_RDONLY WARN message, if I try to
> navigate to the
To hop on what Jon said, if your concern is automatic application of schema
migrations, you want to be very careful with this. I'd consider it an
unsolved problem in Cassandra for some methods of schema application.
The failed ALTER is not what you have to worry about, it's two successful
ALTERs
