You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwhisk.apache.org by OpenWhisk Team Slack <ra...@apache.org> on 2019/12/03 09:32:06 UTC
[slack-digest] [2019-12-02] #general
2019-12-02 07:17:10 UTC - Dominic Kim: Could you share the details?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575271030493000?thread_ts=1575236437.492900&cid=C3TPCAQG1
----
2019-12-02 09:03:57 UTC - Roberto Diaz: I think that you are talking about conductor actions
<https://github.com/apache/openwhisk/blob/master/docs/conductors.md>
If you are using python or JS you also have the possibility to use composer actions which is an abstraction over conductor actions
<https://github.com/apache/openwhisk-composer>
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575277437493200?thread_ts=1575236437.492900&cid=C3TPCAQG1
----
2019-12-02 10:26:29 UTC - giusdp: Hello, I modified the loadbalancer and used
```wskdev controller```
to build/deploy that component.
I then used the make quick-start with docker-compose tool to launch openwhisk, bu it's using the component exactly as it was before my change.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575282389497100
----
2019-12-02 10:27:19 UTC - giusdp: I also put some logging and went to check the tmp/openwhisk/controller/logs, to see if they were being printed, but they are not there. I'm not understanding what I should do to make it use my stuff
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575282439498100
----
2019-12-02 10:54:41 UTC - Rodric Rabbah: Did you try: wskdev deploy
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575284081498500
----
2019-12-02 10:55:51 UTC - Rodric Rabbah: Instead make QuickStart which I think uses specifically tagged images. I will give it a try. Likely you need to tag the new images differently.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575284151000200
----
2019-12-02 14:45:00 UTC - giusdp: How can I do that?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575297900001600
----
2019-12-02 14:47:22 UTC - Rodric Rabbah: `docker tag`
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575298042001800
----
2019-12-02 14:54:37 UTC - giusdp: Thank you, I'll look into it
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575298477002100
----
2019-12-02 16:19:40 UTC - Ali Tariq: @Dave Grove @chetanm, any insights about how do i get all the invokers in use?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575303580002200?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 16:29:49 UTC - Dave Grove: the ingress type should not matter. i would again drop the # of slots per invoker down to something quite a bit smaller and see if you can get the load to spread across multiple invokers. Try something tiny like 16 slots per invoker just to verify that the controller’s load balancer will actually spread your function across multiple invokers.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575304189002400?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 17:03:31 UTC - Ali Tariq: It did not help. I trimmed down to 16 containers per invoker (4096m of `containerpool`) with 5 invoker replicas. Also reduced the workload to only 80 invocation requests but as you can see, the concurrency is being limited by the single invoker capacity! - looking at the pods & invoker-logs, only invoker-0 is being used to handle the requests!
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575306211002600?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 17:18:24 UTC - Dave Grove: should have asked this before. What kind of action are you running? This could be consistent with a “blackbox” (docker) action. By default only 10% (or 1 if there are fewer than 10 invokers) of the invokers will be used to run blackbox actions.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575307104003100?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 17:19:13 UTC - Dave Grove: controlled by whisk.loadbalancer.blackbox-fraction
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575307153003300?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 17:21:06 UTC - Ali Tariq: i have a simple python-runtime `--web true` action being invoked by http Api.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575307266003500?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 17:23:59 UTC - Ali Tariq: ohh ... yes, i am using a custom docker-image with flag `--docker` to use libraries not supported by default.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575307439003700?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 17:26:44 UTC - Dave Grove: ok. that’s it then. You can just change the value of whisk.loadbalancer.blackboxFraction in `values.yaml` and redeploy
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575307604003900?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 17:27:16 UTC - Ali Tariq: Is there any reason why docker actions are treated differently? Also, should i just increase the value to 100% (is there any risk there?)?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575307636004200?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 17:29:27 UTC - Dave Grove: there’s a school of thought that says one may want to segregate blackbox docker actions from managed actions because pulling the images can be slow and can evict the managed runtime images from the docker image cache on the worker node.
+1 : Ali Tariq
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575307767004400?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 17:30:50 UTC - Dave Grove: if you don’t care about that, the system will work just fine mixing blackbox and managed actions on the same invoker. just set the fractions to 100%
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575307850004700?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 17:38:23 UTC - Ali Tariq: Awesome! it's working as expected ... thank you for the help. I would like to add a `Scale-up` section in the kube-deploy documentation (<https://github.com/apache/openwhisk-deploy-kube>) ... right after `verify you openwhisk deployment` section - to document simple scale-up & possible issues one could encounter. Does that make sense? (if yes, i ll open a github issue!)
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575308303004900?thread_ts=1574633042.430600&cid=C3TPCAQG1
----
2019-12-02 17:38:48 UTC - Dave Grove: that would be great, thank you!
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1575308328005100?thread_ts=1574633042.430600&cid=C3TPCAQG1
----