This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-23
Channels
- # announcements (2)
- # beginners (165)
- # boot (11)
- # cider (11)
- # clj-kondo (7)
- # cljdoc (1)
- # cljsrn (5)
- # clojure (120)
- # clojure-dev (21)
- # clojure-europe (3)
- # clojure-france (1)
- # clojure-italy (62)
- # clojure-nl (8)
- # clojure-spec (26)
- # clojure-uk (40)
- # clojuredesign-podcast (1)
- # clojurescript (3)
- # cursive (2)
- # data-science (2)
- # datomic (10)
- # emacs (2)
- # figwheel-main (1)
- # fulcro (17)
- # graphql (5)
- # hoplon (5)
- # jackdaw (15)
- # jobs (2)
- # juxt (1)
- # luminus (5)
- # off-topic (1)
- # onyx (11)
- # pathom (4)
- # pedestal (1)
- # re-frame (4)
- # reagent (11)
- # reitit (1)
- # remote-jobs (5)
- # shadow-cljs (48)
- # spacemacs (2)
- # specter (4)
- # sql (24)
- # tools-deps (25)
- # vim (82)
Hi, there. Can anybody help me with one thing in Onyx? It’s about :onyx/pending-timeout and the sentence bellow: “Asynchronous Barrier Snapshotting fault tolerance technique does not depend on retrying individual segments on a timeout.” Ok, it does not depend on retrying, but indeed is there a timeout inside the code somewhere, where the segments are submitted to retry? If yes, is it possible/recomendable to disable or increase this timeout attribute somewhere? Thanks, Luis
the keyword here is "individual" -- it does not depend on retrying individual segments
however, periodically, it will send a control signal, a barrier, which is then stored on both input and output storage
this essentially makes sure that input and output both agree on what data has been processed
i think, however, the onyx/pending-timeout might be more of an artifact of the pre-ABS days
Yes, it is pre-ABS days. My concern is: eventually, if a block of segments passes the 60sec, it will receive a timeout and then retried, right? Is it defined in some place?