openwhisk-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [openwhisk] tysonnorris opened a new pull request #4659: add config to allow removal of Activation result before storing in some cases
Date Tue, 01 Oct 2019 22:19:21 GMT
tysonnorris opened a new pull request #4659: add config to allow removal of Activation result
before storing in some cases
   In some very specific cases, we can save some db size bloat by not storing Activation result
along with Activation record in db.
   <!--- Provide a concise summary of your changes in the Title -->
   ## Description
   <!--- Provide a detailed description of your changes. -->
   <!--- Include details of what problem you are solving and how your changes are tested.
   When enabled via config, if the following are true, the result portion of Activation document
will not be included in db record that is stored (no change in response seen by client):
   * Activation is blocking
   * Activation response is successful
   * ?debug=true parameter was not included by client
   * timeout not exceeded (a new timeout, specific to this configuration)
   In these cases, results are very unlikely to ever be accessed in database, so this will
save space. It can be useful for cases where there are a large number of significant size
results created (>500k?) which can accumulate 100s of GB or TB of space.
   ## Related issue and scope
   <!--- Please include a link to a related issue if there is one. -->
   - [x] I opened an issue to propose and discuss this change (#4626 )
   ## My changes affect the following components
   <!--- Select below all system components are affected by your change. -->
   <!--- Enter an `x` in all applicable boxes. -->
   - [ ] API
   - [x] Controller
   - [ ] Message Bus (e.g., Kafka)
   - [ ] Loadbalancer
   - [x] Invoker
   - [ ] Intrinsic actions (e.g., sequences, conductors)
   - [x] Data stores (e.g., CouchDB)
   - [ ] Tests
   - [ ] Deployment
   - [ ] CLI
   - [ ] General tooling
   - [x] Documentation
   ## Types of changes
   <!--- What types of changes does your code introduce? Use `x` in all the boxes that
apply: -->
   - [ ] Bug fix (generally a non-breaking change which closes an issue).
   - [x] Enhancement or new feature (adds new functionality).
   - [ ] Breaking change (a bug fix or enhancement which changes existing behavior).
   ## Checklist:
   <!--- Please review the points below which help you make sure you've covered all aspects
of the change you're making. -->
   - [x] I signed an [Apache CLA](
   - [x] I reviewed the [style guides](
and followed the recommendations (Travis CI will check :).
   - [x] I added tests to cover my changes.
   - [x] My changes require further changes to the documentation.
   - [ ] I updated the documentation where necessary.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message