Major Description
While a topology is being redeployed, if it is requested, the client receives an HTTP 404 response. Most clients will not retry when receiving a 404, so the interaction will fail.
If Knox were to respond with a more retry-friendly response (e.g., HTTP 503), then clients could overcome these small windows of unavailability with retries.
The difficult part may be distinguishing topology removal from topology inactivity. I think a deleted topology should still result in a 404.
Attachments
Issue Links
- links to
