The :in-process target-type: the target runs inside Lite's own JVM, as an
object the ClientAdapter opens.
There is one instance, and every worker shares it, the way real clients share one server. It lives in an atom rather than being captured by each worker, because the crash nemesis replaces it mid-run and clients must follow it to the new one.
The `:in-process` target-type: the target runs inside Lite's own JVM, as an object the ClientAdapter opens. There is one instance, and every worker shares it, the way real clients share one server. It lives in an atom rather than being captured by each worker, because the crash nemesis replaces it mid-run and clients must follow it to the new one.
(crash! {:keys [adapter conn crashes lifecycle-lock]})Simulates a crash: destroy the instance and create a new one. Whether that costs any data is up to the target -- which is the interesting question.
For the moment in between, there is no instance; ops that land in that window
find nothing to talk to and are recorded as :info, which is the honest
answer -- Lite can't know whether they took effect.
Simulates a crash: destroy the instance and create a new one. Whether that costs any data is up to the target -- which is the interesting question. For the moment in between, there is no instance; ops that land in that window find nothing to talk to and are recorded as `:info`, which is the honest answer -- Lite can't know whether they took effect.
(crash-count target)How many times this target has been crashed.
How many times this target has been crashed.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |