Creating .lock files in /tmp folder during backup
Hello, folks! I use "cassandra medusa" backup tool and I noticed some issues on some nodes during creating backup. Maybe somebody can help with it?During the backup in the /tmp folder creating a lot of files: -rw-r--r-- 1 rootroot 0 Sep 28 02:11 ffefd10391fbe8b8feb77656c582d3175a0135a63706bdb40fd45ca36e1bdfb7.lock -rw-r--r-- 1 rootroot 0 Sep 28 02:10 fff0600e2ed9312f2a2c2e5105a7d59954bc7f3879659cf8cb0654e0270c77e0.lock -rw-r--r-- 1 rootroot 0 Sep 28 02:56 fff1308a15f7fe8e3e520681f2d080233884ec3a080f8bff2653bc734d318447.lock -rw-r--r-- 1 rootroot 0 Sep 28 02:47 fff13f18e2b3fbc01fa02af91b9da9c4238147d88a50f7a78e710d13544b3d95.lock -rw-r--r-- 1 rootroot 0 Sep 28 02:33 fff84d7a44d81e2ac67dca5ece7076db9642c3345848253d735dab7f418bf50f.lock -rw-r--r-- 1 rootroot 0 Sep 29 02:38 fffae393486cc3d2e1e6f784948ba771067d2d062cf965a2ecedb9be8647eb20.lock -rw-r--r-- 1 rootroot 0 Sep 28 02:05 fffb2fa3ef45676f79ab9e399641dcbc15dc2b39e48825fae172f83c086dcae3.lock -rw-r--r-- 1 rootroot 0 Sep 29 03:00 fffdab6d1b83675e03501ac06e28875f13b6cfa48eb3686237b48eeda3609b97.lock -rw-r--r-- 1 rootroot 0 Sep 28 02:34 24c8e8a1bea11addcff64dfb06511f0e940f0e95bdfda15ddef9579d0b0a.lock There are could be thousands .lock files with zero size. And I don't have any other affects. Only 2 nodes have this behaviour, others all good. Although, there are same configs and versions medusa & cassandra on nodes. Medusa 0.5.1, Cassandra 3.11.12 Any ideas what could be the reason of this? Thanks in advance! With Best Regards, Alexander
Re: Backup cassandra and restore. Best practices
Oh, yes you're right. Sorry for my inattention. I'll check it out. Thank you all! I really appreciate it With Best Regards Alexander N. вторник, 6 апреля 2021 г., 13:50:45 GMT+3, Alexander DEJANOVSKI написал(-а): Yes, Minio is supported by Medusa through the S3 compatible backend.I reckon we need to update the docs with a guide on setting up those backends, but it's pretty much the same as ceph s3 rgw in configuring your medusa.ini :- use s3_compatible as storage backend- set the host, port and region settings appropriately to connect to your Minio install- set the "secure" setting to false (libcloud doesn't support ssl on s3 compatible backends) And you should be good to go.We also have integration tests that use the Minio backend. Cheers, Alex Le mar. 6 avr. 2021 à 12:33, Erick Ramirez a écrit : Minio is a supported type -- https://github.com/apache/libcloud/blob/trunk/libcloud/storage/types.py#L108 On Tue, 6 Apr 2021 at 20:29, Erick Ramirez wrote: This is a useful tool, but we look for smth that could store backups in local S3 (like minio), not Amazon or else.. As I stated in my response, Medusa supports any S3-like storage that the Apache Libcloud API can access. See the docs I linked. Cheers!
Re: Backup cassandra and restore. Best practices
Thank you, Erick!This is a useful tool, but we look for smth that could store backups in local S3 (like minio), not Amazon or else..If I correctly understand, Medusa can't do it. Nevertheless, thank you for your response! With Best RegardsAlexander N. вторник, 6 апреля 2021 г., 11:35:40 GMT+3, Erick Ramirez написал(-а): I'd recommend using Medusa (https://github.com/thelastpickle/cassandra-medusa/wiki) -- an open-source tool which automates backups and has support for archiving to S3, Google Cloud and any S3-like storage. Cheers!
Backup cassandra and restore. Best practices
Hello everyone!We have a new Cassandra cluster, which exists of 5 nodes in 1 DC. Now, I looking for a tool, which could help backup data to S3 or smth locally. Could you help me please with best practices for backing up and restoring? Is it enough to have local snapshots? In my opinion, the better way is copying snapshots to another server also, like S3. How are you implement it? Which tools do you use?Thanks for sharing your answers! With Best RegardsAlexander N. вторник, 6 апреля 2021 г., 10:10:29 GMT+3, manish khandelwal написал(-а): Hi I am struggling to find way to set read_ahead_kb for Cassandra in our Kubernetes environment. Any way by which we can achieve this? My issue is that since PV is mounted in a container and it can have any name depending on partition number. Also wanted to know where it will be set, inside the container or on the host machine? RegardsManish
