clojusc.mesomatic.examples.standard.framework
check-task-abort
(check-task-abort state payload)check-task-finished
(check-task-finished state payload)do-healthy-status
(do-healthy-status state payload)do-unhealthy-status
(do-unhealthy-status state-name state payload)framework-info-map
Documentation forthcoming
get-bytes
(get-bytes payload)get-channel
(get-channel state)get-driver
(get-driver state)get-error-msg
(get-error-msg payload)get-exec-info
(get-exec-info state)get-executor-id
(get-executor-id payload)get-framework-id
(get-framework-id payload)get-master-info
(get-master-info payload)get-message
(get-message payload)get-offer-id
(get-offer-id payload)get-offers
(get-offers payload)get-slave-id
(get-slave-id payload)get-state
(get-state payload)get-status
(get-status payload)get-task-state
(get-task-state payload)handle-msg
multimethod
This is a custom multimethod for handling messages that are received on the async scheduler channel.
Note that:
- though the methods are associated with types whose names match the scheduler API, these functions and those are quite different and do not accept the same parameters
- each handler’s callback (below) only takes two parameters:
- state that gets passed to successive calls (if returned by the handler)
- the payload that is sent to the async channel by the scheduler API
- as such, if there is something in a message which you would like to persist or have access to in other functions, you’ll need to assoc it to state.
healthy?
(healthy? payload)limits
Documentation forthcoming
log-framework-msg
(log-framework-msg framework-id executor-id slave-id payload)run
(run master task-count)This is the function that actually runs the framework.