This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-14
Channels
- # arachne (5)
- # architecture (2)
- # bangalore-clj (7)
- # beginners (96)
- # boot (34)
- # braveandtrue (1)
- # cider (12)
- # cljs-dev (38)
- # cljsrn (59)
- # clojure (326)
- # clojure-dev (35)
- # clojure-greece (1)
- # clojure-italy (6)
- # clojure-russia (47)
- # clojure-spec (16)
- # clojure-uk (25)
- # clojurescript (136)
- # core-async (18)
- # cursive (18)
- # datascript (2)
- # datomic (28)
- # dirac (6)
- # emacs (4)
- # garden (3)
- # hoplon (28)
- # instaparse (1)
- # jobs (4)
- # juxt (1)
- # lein-figwheel (10)
- # liberator (1)
- # mount (3)
- # off-topic (39)
- # om (16)
- # om-next (1)
- # onyx (15)
- # pedestal (9)
- # proton (1)
- # random (1)
- # re-frame (48)
- # reagent (8)
- # ring-swagger (4)
- # rum (3)
- # specter (5)
- # sql (3)
- # unrepl (273)
- # untangled (27)
- # vim (4)
- # yada (7)
@chrisblom it will result in accumulation of garbage segments in storage
unlikely to affect performance substantially, although that may depend on the specific storage
oh, i want to run it, but we didn't run it for a long time as our gc task was misconfigured
Why not Datomic runs gc-storage on regular basis?
why it should be scheduled outside?
14:19:39 2017-03-13 14:19:38.972 INFO default datomic.garbage - {:event :garbage/collect, :dbid "production-2017-01-09-c-cf03505f-7aac-4653-acab-913f4b3a086b", :older-than #inst "2017-01-13T10:31:35.781-00:00", :msec 1.3699999999999998E7, :phase :end, :threw java.util.concurrent.ExecutionException, :pid 9, :tid 1121}
14:19:39 2017-03-13 14:19:38.974 WARN default datomic.garbage - {:message "Cluster gc failed", :pid 9, :tid 1121}
14:19:39 java.util.concurrent.ExecutionException: com.amazonaws.services.dynamodbv2.model.ProvisionedThroughputExceededException: The level of configured provisioned throughput for the table was exceeded. Consider increasing your provisioning level with the UpdateTable API. (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ProvisionedThroughputExceededException; Request ID: STKU1ATRLK677TKLOARC6BVP
14:19:39 Caused by: com.amazonaws.services.dynamodbv2.model.ProvisionedThroughputExceededException: The level of configured provisioned throughput for the table was exceeded. Consider increasing your provisioning level with the UpdateTable API. (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ProvisionedThroughputExceededException; Request ID: STKU1ATRLK677TKLOARC6BVPBBVV4KQNSO5AEMVJF66Q9ASUAAJG)
14:19:39 2017-03-13 14:19:38.975 WARN default datomic.garbage - ... caused by ...
14:19:39 com.amazonaws.services.dynamodbv2.model.ProvisionedThroughputExceededException: The level of configured provisioned throughput for the table was exceeded. Consider increasing your provisioning level with the UpdateTable API. (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ProvisionedThroughputExceededException; Request ID: STKU1ATRLK677TKLOARC6BVPBBVV4KQNSO5AEMVJF66Q9ASUAAJG) at com.ama
also discussed near the bottom of this: http://docs.datomic.com/capacity.html#garbage-collection-deleted-production