Tips & Tricks
Generic tips and tricks to use the platform more effectively
- 1.Synpse will always try to create and pull image first before stopping old application instance. This is done to prevent downtime when operating in the remote environments
- 2.Synpse will always try to restart your application if failed. So there is possibility for constant restarts if OOM or application startup failures happens
- 3.Synpse will cache images locally for 24h by default, so if image is not with the latest tag, updates in the remote registry might not be seen in the application. For updates assured use image versioning
When scheduling and constructing your application minimal downtime might be needed. Consider these situations:
- 1.Edge device is running in the remote location with very poor internet connectivity, where downloading updated image might take long time
- 2.Image registry you are using is experiencing an outage and no new images can be pulled
Both of these scenarios could be reason for application downtime. For this we recommend tune application specification as per your requirements. Few recommendations bellow:
Don't use image tag
latest . Default runtime behavior is to always pull if latest is used. So if you are experiencing outage on registry (due to network or registry itself) you will fail to start. Set
imagePullTimeout in the Application spec (See Application specification) to be representative of how long you expect image pulls to take on. This might help you in certain conditions.If you want agent to always pull the container - set
forcePull. This will instruct agent to always pull image, even when tag is not latestLast modified 1yr ago