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/10/29 09:14:26 UTC
[slack-digest] [2019-10-28] #general
2019-10-28 03:16:53 UTC - Abbie Dowd: Hello, I'm new to openwhisk and am trying to deploy using ansible. I am able to get all to way to deploying controller 0 and then it fails saying the connection is refused (see below). What's strange is that the container is running and I can attach to it. Any idea why the connection would be refused?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572232613126400?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 03:18:46 UTC - Jiang PengCheng: could you show the detail log of controller? it may locates in the `/tmp/wsklogs/controller0/`
+1 : Dominic Kim
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572232726127400?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 03:20:56 UTC - Abbie Dowd: Sure I'll check it out
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572232856127900?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 03:25:53 UTC - Abbie Dowd:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572233153128100?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 03:27:49 UTC - Abbie Dowd: Looks like it might be failing when it attempts to connect to couchdb??
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572233269128500?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 03:27:55 UTC - Jiang PengCheng: it says that your couchdb is unreachable
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572233275128700?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 03:28:40 UTC - Jiang PengCheng: yes, you can try that url to see whether it works
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572233320128900?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 03:29:12 UTC - Abbie Dowd: I tried running curl with that url, and I get the same response
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572233352129100?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 03:31:50 UTC - Jiang PengCheng: now you find out what the problem is, restart or redeploy the couchdb should resolve it, or check the couchdb logs to see the detail reason: `docker logs couchdb`
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572233510129300?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 03:44:39 UTC - Abbie Dowd: I'm sorry looking at the couchdb logs and still I don't really understand what the problem is. This is what the last few lines look like.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572234279129500?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 03:44:48 UTC - Abbie Dowd:
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572234288129700?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 04:15:58 UTC - Dominic Kim: @Abbie Dowd Are you running it on Mac or Linux?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572236158130600?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 04:16:59 UTC - Dominic Kim: Generally CouchDb Ip should not be 127.0.0.1, because the controller runs inside of a container.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572236219132000?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 04:17:22 UTC - Dominic Kim: Surely there is no 5984 port enabled in the controller container.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572236242132800?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 04:18:03 UTC - Dominic Kim: You may want to try with 172.17.0.1 or any docker0 ip.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572236283133600?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 04:22:49 UTC - Abbie Dowd: It's linux. I will try 172.17.0.1. What would be a more appropriate port??
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572236569133800?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 04:35:51 UTC - Chris Wegener: hi. is it true that any action that takes longer than 60 seconds will NOT show up in activation poll?
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572237351134100
----
2019-10-28 05:35:05 UTC - Jiang PengCheng: it seems that you can connect to the CouchDB via 172.17.0.1:5984? and controller use `127.0.0.1:5984`, which is not supposed to be accessable as controller is in a docker container, what's the `hosts` file did you use for the command `ansible-playbook`?
+1 : Dominic Kim
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572240905134200?thread_ts=1572232613.126400&cid=C3TPCAQG1
----
2019-10-28 06:37:15 UTC - Dominic Kim: @Chris Wegener Generally the activation will show up in the end when the activation is over.
white_check_mark : Rodric Rabbah
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572244635134700
----
2019-10-28 11:01:26 UTC - Rodric Rabbah: That’s generally true. However if there are intervening activations that complete before the longer activation and the time cursor advances too far you might miss the results in the poll because it doesn’t back fill into the past.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572260486137000
----
2019-10-28 15:44:22 UTC - giusdp: Hello, I have a question about the load balancer. Does it consider code locality or session locality or other stuff? For what I understood its just a pseudorandom algorithm, it calculates a home invoker and then schedules a function to it if its healthy and available
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572277462139400?thread_ts=1572277462.139400&cid=C3TPCAQG1
----
2019-10-28 16:11:05 UTC - Rodric Rabbah: there is a list of co-primes computed by the algorithm which represents the invoker ids in the system that a specific function may be assigned to
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572279065139500?thread_ts=1572277462.139400&cid=C3TPCAQG1
----
2019-10-28 16:11:41 UTC - Rodric Rabbah: the lb will attempt to schedule to one of those first, and fall back to the home invoker if no suitable index is found otherwise (for example if every invoker is overloaded)
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572279101139700?thread_ts=1572277462.139400&cid=C3TPCAQG1
----
2019-10-28 16:11:54 UTC - Rodric Rabbah: @Markus Thömmes could tell you more
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572279114140000?thread_ts=1572277462.139400&cid=C3TPCAQG1
----
2019-10-28 16:24:18 UTC - giusdp: Yes I found out about that in the comments of the code. Searching around for the state of the art, I saw there are several papers about OpenWhisk and OpenLambda where they propose schedulers that take in consideration the locality of data, code or even sessions.
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572279858140200?thread_ts=1572277462.139400&cid=C3TPCAQG1
----
2019-10-28 16:26:02 UTC - giusdp: I would love to know more about this part of open whisk and if there is any related work planned
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572279962140400?thread_ts=1572277462.139400&cid=C3TPCAQG1
----
2019-10-28 18:22:29 UTC - chetanm: OpenLambda looks interesting. Looks like it has support for direct cgroup based sandboxing in addition to docker based launching. An aspect which we may explore for some light weight usecases
https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1572286949140600?thread_ts=1572277462.139400&cid=C3TPCAQG1
----