How to take a snapshot of an EBS volume with a running RabbitMQ instance?

I use RabbitMQ for an EC2 instance, and I have Mnesia tables on the EBS volume, so when I take a snapshot and try to start another instance with the same data, it seems that the table is being used by another RabbitMQ instance.

The only way around this is to close RabbitMQ for flash / snapshot and then run it back after it is done?

Is there a way to clear files so that they are not locked or forcibly unlocked?

This is not a common problem that I will run into, just curious if there is a better solution.

In order to explain the mistake, I see: timeout_waiting_for_tables.

+3
source share
1

. , LVM, ext3, xfs , LVM, dmsetup man page; , dmsetup suspend/resume

- :

dmsetup suspend <dev> 
ec2-create-snapshot <vol> 
dmsetup resume <dev> 

/ , . Rabbitmq :

.   rabbit_persister.LOG ?   , rabbit_persister.LOG.previous?

. rabbit_persister.LOG - ..previous log , .

, ?

, .

?

rabbit__persister: force_snapshot() Erlang .

force-snapshot Rabbitmq Makefile.

+3

Source: https://habr.com/ru/post/1717090/


All Articles