You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, a quick question: is it possible to make dynamic-dynamodb stop after the first execution? In other words, is there any configuration, or anything that I can do, to make the python process stop after the first loop on the tables matching the table section?
I am not running the script through a daemon.
Thanks!
The text was updated successfully, but these errors were encountered:
It is currently not supported. But I am about to release a new version of dynamic-dynamodb. I will include a command line option (--run-once) that will trigger that behaviour.
I need the "--run-once" option because I run the script in a Java application running in an autoscaling group that has ~8 EC2 instances, and I don't want that it runs on each server, but exactly on one, by specifying a cron expression.
I exploit the optimistic locking of Dynamo DB, combined with ntp synchronization and a cron expression, in order to run the script exactly on one random active node from inside a java job. Thus, I don't have any single point of failure.
Hello, a quick question: is it possible to make dynamic-dynamodb stop after the first execution? In other words, is there any configuration, or anything that I can do, to make the python process stop after the first loop on the tables matching the table section?
I am not running the script through a daemon.
Thanks!
The text was updated successfully, but these errors were encountered: