2020-10-22 09:20:30 UTC - Dominic Kim: We are using Pinpoint for the distributed tracing. <https://github.com/pinpoint-apm/pinpoint> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603358430124500?thread_ts=1603305421.116300&cid=C3TPCAQG1 ---- 2020-10-22 09:21:01 UTC - Dominic Kim: @seonghyun contributed the Akka-http plugin and OpenWhisk plugin to the Pinpoint project. <https://github.com/pinpoint-apm/pinpoint/tree/master/plugins> https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603358461124700?thread_ts=1603305421.116300&cid=C3TPCAQG1 ---- 2020-10-22 09:21:52 UTC - Dominic Kim: We are internally maintaining the plugins but not quite sure they work well with the latest OpenWhisk codes. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603358512125100?thread_ts=1603305421.116300&cid=C3TPCAQG1 ---- 2020-10-22 09:23:00 UTC - Dominic Kim: Since Pinpoint is based on bytecode intsrumentation, it might not work if the traced codes are updated. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603358580125500?thread_ts=1603305421.116300&cid=C3TPCAQG1 ---- 2020-10-22 09:23:47 UTC - Dominic Kim: It would be great to check and update those plugins to make them work with OpenWhisk 1.0.0. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603358627125700?thread_ts=1603305421.116300&cid=C3TPCAQG1 ---- 2020-10-22 09:25:28 UTC - Dominic Kim: This issue was one of the reasons why I implemented the new scheduler. This issue is especially more problematic when you have the limited(fewer) numbers of invokers. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603358728125900?thread_ts=1603305061.114600&cid=C3TPCAQG1 ---- 2020-10-22 09:26:09 UTC - Dominic Kim: Before having the scheduler, we tried to separate the heavy-workloads functions with the others as a fallback. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603358769126100?thread_ts=1603305061.114600&cid=C3TPCAQG1 ---- 2020-10-22 09:26:55 UTC - Dominic Kim: So that frequenty actions are invoked on a kind of "dedicated" invokers while the others are sharing the same invokers. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603358815126300?thread_ts=1603305061.114600&cid=C3TPCAQG1 ---- 2020-10-22 09:27:38 UTC - Dominic Kim: But it's just a naive and transient approach and has many pitfalls.. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603358858126500?thread_ts=1603305061.114600&cid=C3TPCAQG1 ---- 2020-10-22 12:12:25 UTC - Pavel Kravchenko: Excellent. Thank you very much. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603368745126800?thread_ts=1602582237.064000&cid=C3TPCAQG1 ---- 2020-10-22 12:14:27 UTC - Pavel Kravchenko: Is there twitter provider for Openwhisk? To register and fire trigger on each tweet. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603368867128200?thread_ts=1603368867.128200&cid=C3TPCAQG1 ---- 2020-10-22 14:41:00 UTC - Rodric Rabbah: not that i know of https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603377660128300?thread_ts=1603368867.128200&cid=C3TPCAQG1 ---- 2020-10-22 17:25:58 UTC - Brendan Doyle: hmm I'll message you to pick your brain on this on how you managed to separate the heavy workloads. Was it just renaming functions or bringing up and down invokers?
But yea this is our biggest issue hence why I can hardly wait for the scheduler :wink: https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603387558128500?thread_ts=1603305061.114600&cid=C3TPCAQG1 ---- 2020-10-22 22:20:40 UTC - parichehr vahidinia: @Dave Grove I edited invoker-pod.yaml as follows: `-name:"CONFIG_whisk_containerProxy_timeouts_idleContainer" value{{.Values.whisk.containerProxy.timeouts.idleContainer }}` and values.yaml as follows: ```whisk: containerProxy: timeouts: idleContainer: "3minutes"``` but still the idle-container value is 10 minutes https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1603405240129100?thread_ts=1603306004.118000&cid=C3TPCAQG1 ----
