View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006245 | MMW v4 | Properties/Auto-Tools | public | 2010-01-13 06:31 | 2010-10-29 18:08 |
| Reporter | michal | Assigned To | |||
| Priority | none | Severity | minor | Reproducibility | unable to reproduce |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 4.0 | ||||
| Summary | 0006245: Auto-Tag from Web: request is sometimes throttled | ||||
| Description | Auto-Tag from Web sometimes failes with the error "Request from 1EYXVSY9HM4XCVN8GK82 is throttled." This could be caused by more than one request per second per IP address. In this case, we should wait a little and try to make another request attempt (e.g. 2s later), instead of showing this error immediately. | ||||
| Additional Information | http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=7684 http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=45847&p=239604 Described in Knowledgebase under: http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=138 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1307 | ||||
|
|
Fixed in build 1301. MM does max. 4 successive request attempts now, after the first error response waits 2s before retrying, then 4s, then 8s and then writes error message, the user could try again later. I could confirm, that this error could occure when requesting many times in a very short period from one IP address, so parallel searching on more computers behind one IP address could cause this error. |
|
|
If it is not trivial can you merge it also to 3.2.1 release? If yes just resolve it again and I'll tool over. |
|
|
Resolving. It is not trivial to merge it to 3.2.1, it would be too risky. |
|
|
For future insurance can you make small change to be more certain in case multiple PCs are accessing. For Second and Third retry, maybe we could use different logic and wait 1-8 seconds selected randomly. Do you agree that http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=138 should be enough? |
|
|
It is hard to say, if the random interval would give better results. But I could change it that way. I'm not sure what 'reinitialize "Auto-Tag from Web".' means, I would say just "Try again later" |
|
|
You are right I corrected KB article. If it is trivial to add you should add it as two PC using same intervals will generate same error again. I'll leave it on you for decision as that is lower priority. |
|
|
Amazon servers don't return this error regularly, I think it depends on their actual load somehow. I can adjust the intervals after more testing, based on the testing results. For now, I will change the waiting time to random number, taken from some interval. I will extend that interval for each successive attempt. |
|
|
So from the build 1307 the waiting times in this case will be random, taken successively from intervals 1-2s, 1-4s, 1-8s and 1-16s. |
|
|
Fixed in 1307, resolving. |
|
|
It is hard to replicate, is it possible to add this to auto regression testing where testing dunit code will try to replicate faster requests? Verified 1318 |
|
|
Test is possible, but it is hard to replicate from one computer, anyway. I think feedback from users, who reported this problem, will be enough and more valuable. |
|
|
Maybe I'm wrong but doing several simultaneous queries to Amazon in one sec (10 for example) within regression testing should give us enough feedback does fix work? |
|
|
It could detect, that the fix does not work good (if the error occures again), but it cannot verify, that it does work always. The error depends on Amazon server behavior, e.g. I have made even more then 10 queries in a very short time and the error did not occure.. Well, I could make the test later, maybe it could help to adjust waiting intervals, but I think it has quite low priority. |
|
|
No need. I can't replicate it either. and today I tested with 100 queries using my own HTTP app and MM generated query. We can reopen if someone reports that it happened again. Resolved and Closed as it is tested with 1318 |
