Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Configure Greengrass v2 to restart a lambdaFunction component that terminates

0

We've migrated from Greengrass v1 to Greengrass v2 and our component is based on a long running lambdaFunction (Java 11 runtime) that runs with isolation mode NoContainer. It all works quite well...

One of the core libraries we can't avoid using is prone to deadlock and the way we worked around this in Greengrass v1 was to terminate the application (with System.exit()) relying on Greengrass v1 to restart the application and that worked well enough.

Greengrass v2 however will not restart the component once it terminates. Is there a way to configure Greengrass v2 to restart the component if it terminates?

Topics
Internet of Things (IoT)
Tags
AWS IoT Greengrass
Language
English

asked a year ago115 views

1 Answer
1

Unfortunately there is not a direct way to configure GGv2 to restart the lambda component after termination.

Potentially, a similar behavior could be achieved if you have the lambda triggered by a pubsub topic and then have a new generic component that you've written publish to said topic to re-trigger the lambda. However, it would also make sense to just rewrite the lambda component as a generic component at this point as well to have the behavior you want.

AWS

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content