Comment 4 for bug 1793676

Revision history for this message
John Griffith (john-griffith) wrote :

@Chhavi
Yeah, the only thing is that just having it configured doesn't mean it's actually set up properly and working. A driver would be smart if it actually verifies it has connectivity and the connection settings work properly.

I get that the stats call might be expensive for *some* backends, but I'm just not completely sure how serious that is. Also, given the fact that this is a periodic and it's just going to run again in 60 seconds (or whatever your period is set to) I'm not sure how much this really saves you?

I wouldn't object to a replication specific init I guess; but I'm still having a hard time figuring out the real value. Fact is, we can't do anything with that backend until a full stats update call anyway to get all the capacity info etc.

The property is fine, but that comes with the stats so I'm not sure what you're thinking there, unless you are wanting to just limit the response? One other thing to keep in mind is you could do something like have the second call set refresh=False if you're worried about taxing the backend?