This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-22
Channels
- # adventofcode (78)
- # announcements (12)
- # babashka (2)
- # beginners (116)
- # calva (20)
- # cider (17)
- # clj-kondo (15)
- # cljs-dev (51)
- # clojure (32)
- # clojure-android (1)
- # clojure-dev (4)
- # clojure-europe (91)
- # clojure-gamedev (1)
- # clojure-italy (2)
- # clojure-nl (1)
- # clojure-spec (12)
- # clojure-taiwan (1)
- # clojure-uk (10)
- # clojurescript (9)
- # conjure (3)
- # cryogen (4)
- # cursive (4)
- # data-science (1)
- # datomic (5)
- # depstar (5)
- # fulcro (39)
- # google-cloud (2)
- # kaocha (2)
- # malli (7)
- # off-topic (3)
- # pathom (3)
- # pedestal (5)
- # re-frame (19)
- # rewrite-clj (54)
- # ring (3)
- # shadow-cljs (12)
- # spacemacs (12)
- # specter (3)
- # tools-deps (63)
i'm still having an issue with deleting compute or query groups of a datomic cloud system (version 732-8992
)
the stack hangs on deleting the LambdaSecurityGroup
, because it's still attached to ENIs.
deleting DatomicLambdaRole
fails with:
Cannot delete entity, must delete policies first. (Service: AmazonIdentityManagement; Status Code: 409; Error Code: DeleteConflict; Request ID: bfac688c-d62e-4d52-82ed-625c81837144; Proxy: null)
and DeleteDatomicLambdaEnis
fails with:
Failed to delete resource. See the details in CloudWatch Log Stream: 2020/12/22/[$LATEST]d78708ea11a4499193ea28600b96feab
but i couldn't find that log stream, so not sure what does it say.
i've asked about it roughly a year ago, but didn't seem to get an answer:
https://clojurians-log.clojureverse.org/datomic/2019-12-14
does anyone have any suggestions to prevent this happening?I'm running lots of transactions into a Datomic Solo topology. In the CW logs, I'm seeing an alert logged every few seconds that looks something like the below. Any idea why this would be occurring?
Hey @U083D6HK9, the error here is saying the Indexer was unable to complete a DDB operation to read a newly created index from DDB. I have a hunch that you've saturated your DDB provisioned operations for a Solo Topology.