RE: [PATCH V3] SA Busy Handling

Hefty, Sean
2010-12-03T22:24:39Z

> However I think I would like to have at least some idea of what the
> smarter way to handle "busy" responses will be. If we're always just
> going to treat them like timeouts, then it seems the SA would be smarter
> to avoid sending them in the first place.

I'm making stuff up here, but one possible difference between handling busy response versus a timeout could be: a busy response increases the timeout before a mad is retried and wouldn't necessarily decrease the total number of retries that would be attempted. A timed out mad would be retried immediately, with a longer timeout on the back-end.

However, I can't think of a reason why it would be better for the SA to respond with busy under heavy load rather than just dropping the mad. If busy conveyed some sort of retry time, that would be nice.

- Sean