Hi,

The purpose of this topic is to try to understand the scope of 
Machinekit/machinetalk.

Specifically, on the topics of heartbeat and connection 
detection/maintenance and state detection/maintenance between components.

My (somewhat dated) experience is that these topics (connection and state 
monitoring/maintenance) are really hard to do properly:
The MPI specifications should be an eye-opener and the maillist discussions 
some 20 years ago had very robust exchanges about whether it was even 
possible to do what the specs were requiring - this was before the CAP 
conjecture/theorem was even a topic - from memory they were running up 
against exactly those constraints - anyway that is a separate topic I'll 
post shortly.

Is there a reason that MK/MT does not require that MT middleware delegate 
connection and state maintenance to services/applications such as keealived 
(with check and notify scripts), heartbeat or corosync?

Related to this:
What is there is the MK/MT requirements that is going to prevent MK/MT 
becoming a cluster resource manager e.g pacemaker?

My preference is that the MK/MT components must not implement connection 
detection/maintenance nor state detection/maintenance.  Rather they must 
restart and try again, possibly using some check point convention that is 
understood by all components.  

Of course I don't really have a deep insight into critical MK/MT 
scenarios/use-cases.

Right now I'm writing some FSM, as PoC, and these questions are bugging me 
- where do I stop.
I really just want to have the component check in with some authoritative 
(local) source about whether the other component is there, and if not a 
definitive yes. Restart and try again. KIS.

Appreciate any insights.

Best wishes
Hedge

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to