Fork me on GitHub
#onyx
<
2019-07-23
>
luiseugenio16:07:06

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

lmergen18:07:59

the keyword here is "individual" -- it does not depend on retrying individual segments

lmergen18:07:32

however, periodically, it will send a control signal, a barrier, which is then stored on both input and output storage

lmergen18:07:54

this essentially makes sure that input and output both agree on what data has been processed

lmergen18:07:11

this happens periodically, e.g. every 15 seconds

lmergen18:07:17

i think, however, the onyx/pending-timeout might be more of an artifact of the pre-ABS days

👍 4
luiseugenio18:07:16

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?

lmergen19:07:24

yes if the block passes 60s, a timeout occurs and an exception for the task is thrown

lmergen19:07:37

Onyx then attempts to restart the task

lmergen19:07:45

and recover from the last checkpoint

lmergen19:07:34

the code to handle this is fairly deep inside Onyx, but you can see it surface in e.g. all the plugins that have to implement these check pointing and recovery functions

👍 4