Description of problem: Calamari should emit events whenever there is a change in PG state, it should give information like old-state, new-state, PG id and other relevant info. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This is the kind of data I have access to Darshan. I can send events for pg state changes that effect particular pools, particular OSDs and global state. I am a little concerned that if you just blindly pass through each change the meaning will get lost in too many notifications. What are your thoughts? { "all": { "active+clean": 192 }, "by_osd": { "0": { "active+clean": 192 } }, "by_pool": { "0": { "active+clean": 64 }, "1": { "active+clean": 64 }, "2": { "active+clean": 64 } } }
(In reply to Gregory Meno from comment #4) > This is the kind of data I have access to Darshan. > I can send events for pg state changes that effect particular pools, > particular OSDs and global state. I am a little concerned that if you just > blindly pass through each change the meaning will get lost in too many > notifications. What are your thoughts? > > { > "all": { > "active+clean": 192 > }, > "by_osd": { > "0": { > "active+clean": 192 > } > }, > "by_pool": { > "0": { > "active+clean": 64 > }, > "1": { > "active+clean": 64 > }, > "2": { > "active+clean": 64 > } > } > } I agree with your concern, it doesn't make sense to notify for each state change. I had a discussion with monitoring guys, and they periodically(10min) sync the PG state detail. skyring can rely on this to get the updated PG state information. So, its okay to not have this feature.
Nishanth, I moved this 2.1 on guidance from Darshan. I wanted to confirm that you saw it and agree with the action.
same statement as comment 6 to you Jeff
Ack. I am fine with this and go ahead with this plan if Jeff in agreement
(In reply to Nishanth Thomas from comment #8) > Ack. I am fine with this and go ahead with this plan if Jeff in agreement I am fine with this. PG state change notifications will be too chatty if we don't limit them. The only question I have is: Gregory/Nishanth are there any exceptions to this rule, i.e. where something is so bad we need to immediately notify a state change?
No plans to provide this functionality