Subtask #3069
closedFeature #2611: mon: Single-Paxos
Subtask #2621: mon: Single-Paxos: synchronize the MonitorDBStore of oblivious monitor
Subtask #2736: mon: Single-Paxos: Sync: Implement message passing
mon: Single-Paxos: messaging: log MMonSync messages for offline matching
0%
Description
Keep a log of sent/received MMonSync messages, obtainable through the admin socket, for offline matching.
Completing this with a script that would describe the messages effects on the receiving end, would enable us to pinpoint incorrect behaviors.
For instance, stating that a MMonSync::OP_START would cause a MMonSync::OP_START_REPLY with or without the MMonSync::FLAG_RETRY set, would allow us to infer if something in the code path is wrong if we ended up receiving any other kind of MMonSync::OP_*.
Updated by Joao Eduardo Luis over 11 years ago
If we really want to do offline matching, this can be done using just the logs. This could be interesting however for teuthology, as part of the QA effort.
As I have a soft-spot for this kind of ideas and tend to believe this kind of automation is always the best*thing*in*the*universe, does anyone want to chime in?
Updated by Joao Eduardo Luis about 11 years ago
- Status changed from New to Rejected
- Translation missing: en.field_remaining_hours set to 0.00
This is not something that we really need, and it's usefulness is very much close to none. Logs are more than enough to check what's going on. And anything close to useful in this regard would require us to pour a considerable amount of effort, and would probably be done on the messenger level anyway.