Thanks for the update - will review the PR again.
On Mon, Nov 26, 2018 at 9:26 AM Christian Bickel wrote:
> Hi Rodric,
>
> thanks a lot for your feedback. I changed my PR to use the quota instead of
> switching it off completely.
>
> Now the controller checks, how many activations have been
Hi Rodric,
thanks a lot for your feedback. I changed my PR to use the quota instead of
switching it off completely.
Now the controller checks, how many activations have been written in the
current minute. The remaining quota is passed on. On trying to save an
activation (of a trigger, a sequence
Thanks for the additional information Christian - I took a look at the PR
and added a few comments. I think you can approach this as another quota
(number of activations stored per minute or per hour) and setting the quota
to 0 would disable all stores.
I also don't like the way this was done in
Markus, Christian - it's not clear to me from the first note if Christian
is proposing excluding all activation data (including the metadata, not
just the logs) from couchdb, for a namespace. I think this is a very crude
patch and wonder why we don't address the underlying issue instead. I
haven't
Hi Markus,
thanks a lot for your response.
I definitely agree, that all limits should be reviewed and reworked.
The reason why I've chosen this limit as per-namespace-limit and not as
per-action-limit is, to give the operator of Openwhisk the ability to
protect the own database.
If the limit
Hi Christian,
given the recent work towards getting logs to a separate store to relieve
CouchDB and to make it possible to move it into a store that's more
appropriate for logging load and some other bits that are already
implemented (removing the DB based polling, being able to disable log
