we should retry swift auth for each chunk upload
Currently, if we want to upload a large image file from glance to swift and the auth token is about to expire, it will result into 401. However, if we fetch a new token for each chunk we upload it would be a much safer choice. There can be some optimizations here like:
- we look for the expiration time within the eventlet thread and recreate a new token when the old one is about to expire
We can cache the token if needed and set the expiry time in the cache.
- Or, we can try to have a Retryable error raised within the exception and that way either a new thread can be spun up for uploading the remnant chunks.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Nikhil Komawar
- Direction:
- Approved
- Assignee:
- Hemanth Makkapati
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Nikhil Komawar
Related branches
Related bugs
Sprints
Whiteboard
I like the idea of retrying on such a failure if we are pretty certain the error is related to the token expiring. I'm not sure about needing another thread, to continue.
markwash wishlist 2014-02-18
2015-10-12: (nikhil) this is being discussed separately and I guess we will have a new BP soon. So, marking this as obsolete.
