ActionQueueCommand may need to timeout and retry
Bug #556507 reported by
Natalia Bidart
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu One Client |
Won't Fix
|
Medium
|
Ubuntu One Foundations+ team | ||
Bug Description
Having an ActionQueueCommand that doesn't receive an answer from the server results on a command that never finishes.
We should consider to add timeouts to ACQ. Setting this timeout value is not trivial, since the time that an ACQ takes depends on how fast/slow is the server response.
| Changed in ubuntuone-client: | |
| assignee: | nobody → Ubuntu One Foundations+ team (ubuntuone-foundations+) |
| tags: | added: foundations+ |
| tags: | added: chicharra |
| Changed in ubuntuone-client: | |
| importance: | Undecided → Medium |
| tags: | added: chicharra-maverick |
Revision history for this message
| Facundo Batista (facundo) wrote | #1 |
| tags: |
added: chicharra-natty removed: chicharra-maverick |
| tags: |
added: chicharra-oneiric removed: chicharra-natty |
| Changed in ubuntuone-client: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
And what action should we take in case of the timeout?
- Trigger the command finalization in ERROR, with a specific error for the timeout? We need to analyze this in consideration of the whole Sync behaviour... for example, an AQ_MAKE_FILE_ERROR will put the file in conflict... do we prefer that instead of a stuck client?
- Disconnect the client and connect again? This will be very robust, but if the timeout happened because the server is under an incredible load, disconnecting and reconnecting will worse the problem (OTOH, if the timeout is, say, one hour, it will not be because load).
- Something else?