How to remove dynamic shovels (that are terminated)

[Raul Kaubi]

Hi

rabbitmq 3.6.6

I have a problem with certain queues, that I recently deleted. When I restart rabbitmq-server service, then these queues all return. Now I figured out that this is probably because of these dynamic shovels (at least these 4 are the ones that keep coming back)

This is getting really annoyed.

Is it posible to get rid of these..?

[root@XXXXXXXXX~]# rabbitmqctl eval 'rabbit_shovel_status:status().'

[{{<<"/">>,<<"Move from ha.ettest.logi">>},

  dynamic,

  {terminated,{shutdown,autodelete}},

  {{2018,4,27},{20,5,52}}},

 {{<<"/">>,<<"Move from ha.ettest.teavitus">>},

  dynamic,

  {terminated,{shutdown,autodelete}},

  {{2018,4,27},{20,5,52}}},

 {{<<"/">>,<<"Move from ha.ettest.oigus">>},

  dynamic,

  {terminated,{shutdown,autodelete}},

  {{2018,4,27},{20,5,52}}},

 {{<<"/">>,<<"Move from ha.ettest.paet">>},

  dynamic,

  {terminated,{shutdown,autodelete}},

  {{2018,4,27},{20,5,52}}}]

Regards

Raul

[Sean Nolan]

You can do it in the Shovel Management UI, but shovels are stored as parameters, so you can use rabbitmqctl to clear the parameter for the shovel like this:

rabbitmqctl clear_parameter shovel <your_shovel_name>

Sean

[Raul Kaubi]

Hi

But where do I get my shovel_name for dynamic shovel..?

I tried this:

[root@XXXXXXX~]# rabbitmqctl clear_parameter shovel "Move from ha.ettest.logi"

Clearing runtime parameter "Move from ha.ettest.logi" for component "shovel" ...

Error: Parameter does not exist

[Michael Klishin]

It is required when a dynamic Shovel is created:

http://www.rabbitmq.com/shovel-dynamic.html.

Take a look at https://github.com/rabbitmq/rabbitmq-shovel-management, it can be useful.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Sean Nolan]

I have seen that happen before - is your shovel is created in a cluster? If so, what I have found is that if I create the shovel again on the cluster node where it is reported as terminated and then delete it, it will get cleaned up correctly. When you create it again you don't have to create it as a fully working shovel, you can use a fake target, just create it with the same name as the one that is showing as terminated - "Move from ha.ettest.logi" - and then you'll be able to delete it.

Michael, this is probably a bug with how shovels get deleted in clusters?

Sean

[Michael Klishin]

Without a way to reproduce I cannot know if we'd consider it a bug.

--

You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Sean Nolan]

I can try to repro on Monday, but I'm pretty sure it happens if you clear the shovel on a different node in the cluster to the one where it is running. The parameter gets removed from the cluster so the shovel is deleted but it shows as terminated on the node where it was running even though it is deleted and no longer exists.

Sean

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Michael Klishin]

Shovels react to parameter changes and those are replicated cluster-wide. I cannot think of a connection

but if you have a way to reproduce, we will take a look.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Raul Kaubi]

Hi

Yeah, it is clustered environment.

Unfortunately, I already managed to get rid of these dynamic shovels by disabling rabbitmq-shovel plugin on both nodes and then re-enabling it again, since this clear_parameter did not work for me.

I can also check on next week, perhaps I can also reproduce it somehow.

Regards

Raul