Lambda trigger fails to connect with event source using RabbitMQ

0

I've got an issue related to lambda triggering from Amazon MQ for RabbitMQ. In my case everything works fine until RabbitMQ will be rebooted (or runs into maintenance window). In trigger details I can see then message: last processing result: PROBLEM: Failed to connect with event source.

And in Rabbit logs::

closing AMQP connection <0.21044.6> (10.0.25.82:3459 -> 10.0.17.86:5672):
missed heartbeats from client, timeout: 30s

The only one way to fix this is to reenable trigger in lambda configuration. Issue does not happen on every reboot, it's needed to perform it several times (every 3-4 reboots I think). Does anyone has an idea what's going wrong here?

  • As Uchiha_Madara mentioned, Every Amazon MQ broker has a weekly 2-hour maintenance window during which changes are applied. These changes can include broker version updates, configuration changes, or patching of the operating system and other system software. You can minimize downtime during maintenance by using Multi-AZ brokers. (i.e active/standby deployments for high availability)

已提问 2 年前1243 查看次数
1 回答
1

Hi,

There is nothing wrong with Amazon MQ maintenance window. It updates your service with latest versions & install security patches if any available.

You need to implement pattern Amazon MQ active/standby broker for high availability

Maintenance window will first try to install the patches/updates on standby broker. After that it installs on Active broker. During this phase, standby broker will handle the traffic without any downtime.

AWS
已回答 2 年前
  • It's staging environment - I don't need HA in this case. I understand that instance will be unavailable during maintenance window or during reboot. I'm completely ok with that.

    I do not understand why lambda trigger does not go back automatically to work after RabbitMQ downtime. It's needed to reenable it.

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则