Backpressure for slow activation storage in Invoker

Hi Team, When rate of activation is high (specially with concurrency enabled) in a specific invoker then its possible that rate of storage of activation in ArtifactStore lags behind rate of activation record generation. For CouchDB this was somewhat mitigated by using a Batcher implementation

[slack-digest] [2019-06-19] #general

2019-06-19 19:00:28 UTC - rawkintrevo: hey- not sure if any of y'all are bikers but I did a thing then blogged about it- Apache OpenWhisk- keeping people safe heart : Rodric Rabbah

[slack-digest] [2019-06-19] #composer

2019-06-19 09:19:59 UTC - Bruno Girin: Thanks @Olivier Tardieu I'll do that then! https://openwhisk-team.slack.com/archives/C7DJNS37W/p1560935999004900

Re: [DISCUSS] - prepare to release OpenWhisk catalog

+1 to everything Rodric said! On Mon, 17 Jun 2019 at 14:07, Rodric Rabbah wrote: > > If the weather package is functional and can run with newer node kinds then > I’d favor keeping it. > > I’d favor removing the combinators as we have composer now and we didn’t > document them properly (my

Re: openwhisk distributions via dockerhub

On Wed, 19 Jun 2019 at 20:44, David P Grove wrote: > > 3. Once we have addressed (1) and (2), we should consider opening a legal > discuss thread to see if we can continue to use /u/openwhisk (with clear > branding that /u/openwhisk is an official distribution channel from the > Apache OpenWhisk

Re: openwhisk distributions via dockerhub

>> 3. Once we have addressed (1) and (2), we should consider opening a legal >> discuss thread to see if we can continue to use /u/openwhisk (with clear >> branding that /u/openwhisk is an official distribution channel from the >> Apache OpenWhisk (P)PMC) or if we must migrate to

Re: Openwhisk in a standalone runnable jar (#4516)

> What's the performance like on startup time It starts in < 5 secs. So far no major blocking issue apart from fetching docker logs on Mac. Current approach of directly reading the log json does not work. So need to have a mac version which uses `docker logs` command to somewhat handle such a

Re: Backpressure for slow activation storage in Invoker

Overflowing to Kafka (option b) is better. Actually I would dump all the activations there and have a separate process to drain that Kafka topic to the datastore or logstore. There is another approach of routing the logs directly to a logstore without going through the invoker at all. IBM may

Re: Openwhisk in a standalone runnable jar (#4516)

That is mind-blowingly cool! What's the performance like on startup time? On Thu, 20 Jun 2019 at 06:14, Carlos Santana wrote: > > Genius! > https://www.adminsub.net/tcp-udp-port-finder/whisker > > > - Carlos Santana > @csantanapr > > > On Jun 19, 2019, at 12:30 PM, David P Grove wrote: > > > >

Re: Re: [ACTION REQUIRED] Nominations for PMC Chair for TLP graduation resolution

+1 on either Dave or Rodric taking the chair. Both are excellent candidates and ideally suited to the role. On Wed, 19 Jun 2019 at 20:56, David P Grove wrote: > > Rodric Rabbah wrote on 06/19/2019 06:39:19 AM: > > > > A one year rotation makes sense to me. > > Big +1 on planning for rotation. >