update-status interval per application (variable interval)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Hi,
It is a wish-list request.
Data Platform develops a lot of charms for statfull DB applications.
For the list of reasons we have to change the default 'update-
> https:/
```
Further we highly suggest configuring the status hook to run frequently. In addition to reporting the primary, secondaries, and other statuses, the status hook performs self healing in the case of a network cut. To change the frequency of the update status hook do:
juju model-config update-
Note that this hook executes a read query to MongoDB. On a production level server this should be configured to occur at a frequency that doesn’t overload the server with read requests. Similarly the hook should not be configured at too quick of a frequency as this can delay other hooks from running. You can read more about status hooks here.
```
It is no way for production juju models with a lot of applications (e.g. Charmed Kubeflow). Most of those applications are stateless and do not require short `update-status` interval.
It is a request to create ability to make `update-status` configurable per application.
Another idea is to allow apps to request (temporary) shorter `update-status`, e.g. on handling backups (to show the progress), during cluster resilvering/
The last proposal is to create socket/
When charm is idle, there is no need in short `update-status` interval, while during the workload reconfiguration activity the default interval 5 minutes is huge. It causes bugreports like:
https:/
Thank you in advance!
P.S. 'update-
https:/
Changed in juju: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
tags: | added: config hooks |
tags: | added: canonical-data-platform-eng |