You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been toying with verifying Metafora's correctness via etcd (in part using https://github.com/lytics/etcdlog), but in order to analyze the correctness of Metafora's behavior I need to be able to compare etcd's view-of-the-world with Metafora's.
To this end I'd like to add machine readable Trace events similar to the responses returned from an etcd watch. This should allow us to construct a Call-Me-Maybe-esque history to verify such constraints as:
Tasks are run on exactly one node at a time
During normal operation
During partitioning from broker, tasks are released before claim expires
Tasks are started in a timely fashion (any latency over 1s from task submission to claim seems fishy)
Types
typeTracestruct {
Timestamp time.TimeHoststringNamespacestringTaskIDstringDescriptionstringState statemachine.State`json:"state,omitempty"`Progressinterface{} //TODO what type?
}
typeTracerinterface {
// return an error for testing/debugging, but don't expect people to check it.// nothing for callers to do about failuresEmit(tTrace) error
}
The text was updated successfully, but these errors were encountered:
I've been toying with verifying Metafora's correctness via etcd (in part using https://github.com/lytics/etcdlog), but in order to analyze the correctness of Metafora's behavior I need to be able to compare etcd's view-of-the-world with Metafora's.
To this end I'd like to add machine readable Trace events similar to the responses returned from an etcd watch. This should allow us to construct a Call-Me-Maybe-esque history to verify such constraints as:
Types
The text was updated successfully, but these errors were encountered: