This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-17
Channels
- # adventofcode (23)
- # announcements (2)
- # aws (11)
- # babashka (181)
- # beginners (59)
- # chestnut (2)
- # clj-kondo (9)
- # clojure (90)
- # clojure-brasil (2)
- # clojure-europe (18)
- # clojure-italy (24)
- # clojure-nl (9)
- # clojure-spec (3)
- # clojure-uk (28)
- # clojured (4)
- # clojuredesign-podcast (3)
- # clojurescript (12)
- # community-development (49)
- # core-async (49)
- # cryogen (5)
- # cursive (16)
- # data-science (1)
- # datascript (7)
- # datomic (54)
- # defnpodcast (4)
- # events (2)
- # figwheel-main (14)
- # fulcro (139)
- # graphql (1)
- # jobs-discuss (6)
- # kaocha (1)
- # luminus (2)
- # malli (3)
- # music (1)
- # off-topic (34)
- # pathom (24)
- # re-frame (13)
- # reitit (5)
- # shadow-cljs (8)
- # test-check (6)
Is there a recommended way to be able to call large numbers (more than 64) of lambdas with aws-api
?
Initially I ran into the limit from Cognitect's HttpClient, and I tried creating more AWS lambda clients (suggested in this issue: https://github.com/cognitect-labs/aws-api/issues/98)
However, we've had servers falling over in production because the file descriptor limit is exceeded. Testing at the REPL, it does look like when a client is created for AWS lambda, file descriptors are not released. Should I be doing something to close the client? (Doesn't look like there's a .close
method.) on the aws client.
Might be related to this issue: https://github.com/cognitect-labs/aws-api/issues/109
i ran into the same issue 🙂
tried to run 128 lambdas at once and results were failures to execute them 😞
for the leaks of filehandles, doesn't (aws/stop s3)
release them ?
rather unconventional ...
seems to do it for me
small test i ran
@U7GK705MM i think this should at least help you put out the fire 🙂
Looks like aws/stop
does the trick. Thanks @kulminaator.
Right there in the README too, I just missed it. "Invoke cognitect.aws.client.api/stop
on the client if you want it to shut down any resources it and its http-client are using."
Looks like aws/stop
does the trick. Thanks @kulminaator.