Bugzilla – Full Text Bug Listing
| Summary: | Find and Install... fails if one of update mirrors fails | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Elijah Epifanov <elijah.epifanov> |
| Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Platform-Update-Inbox <platform-update-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | denis.roy, eclipse-bugs, MQuinlan, oliver, pollentierk, rajendarreddyj |
| Version: | 3.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | obsolete | ||
|
Description
Elijah Epifanov
at what point during your update this happened? Update manager fails when one of the mirrors fail (timeout, 404 error, etc.) I have experienced this issue too...it's rather annoying. Especially when I sit here for about 15 minutes waiting for the updates to download, just to get an "Update Failed" error and have to start downloading all over again, and hope that there's not going to be another failed update. I agree with Elijah, that the updates should be downloaded in parallel. All PC's support multiple FTP connections...why not utilize this? Just initiate a few threads to download the files from multiple update sites. But then again, this is a problem with most software with update capabilities. For example, Windows Updates, yum and apt-get all download updates one at a time, rather than downloading multiple updates at the same time. *** Bug 182268 has been marked as a duplicate of this bug. *** *** Bug 158424 has been marked as a duplicate of this bug. *** I don't think the solution is to use parallel downloads, but to use another mirror if one mirror fail. Many people can be against parallel downloads, because not all have fast/cheap connections. Also, don't cancel the update procedure until all mirror have errors. Thanks (In reply to comment #0) > I think it would be better to try another mirror instead of throwing an error. > And it will be great if Eclipse contacted update sites in parallel, not in > sequence. >>>...Many people can be against parallel downloads Whoa Oliver! Don't punish the rest of us with high speed connections, the world will just get faster and faster from here. At least let us configure HOW MANY parallel downloads we want. Better would be to AUTOCONFIGURE and track the speed of the download, then open up another channel when you exceed 200kbs or so. Slow pokes would NEVER see another channel and the fast lane would move even faster. (I am ready for my 2 Gbs connection now.) Here is some additional information I am getting during updates, this doesn't look like a mirror to me. Is something broken: Unable to access "http://download.eclipse.org/technology/emft/updates/". Unable to access site: "http://download.eclipse.org/technology/emft/updates/" [Server returned HTTP response code: "403 Forbidden" for URL: http://download.eclipse.org/technology/emft/updates/.] Server returned HTTP response code: "403 Forbidden" for URL: http://download.eclipse.org/technology/emft/updates/. Unable to access site: "http://download.eclipse.org/technology/emft/updates/" [Server returned HTTP response code: "403 Forbidden" for URL: http://download.eclipse.org/technology/emft/updates/.] Server returned HTTP response code: "403 Forbidden" for URL: http://download.eclipse.org/technology/emft/updates/. It would indeed actually make the Update Manager usable. Because now, timeouts are really to frequent, causing the entire update process to fail after 15 minutes time after time. (or one needs to try to press cancel, it it likes to respond). Problems like these bug 198282, bug 165311, bug 166810 , bug 147803 , ... which seem very frequent, would not be that critical. Now, one single timeout causes the entire update process to roll back, or hang. One failing server should not fail the entire update; it should just continue with the updates, plugins, or servers it actually COULD connect to... Give that this was entered and last commented before p2 was in use, is it even relevant anymore? Eric, all bugs in the Platform Update component are unrelated to p2. If an issue is relevant to p2, it will have a separate bug in the p2 component. I am planning to close most Update Manager bugs once 3.5 has shipped. (In reply to comment #11) > Eric, all bugs in the Platform Update component are unrelated to p2. If an > issue is relevant to p2, it will have a separate bug in the p2 component. I am > planning to close most Update Manager bugs once 3.5 has shipped. > Got it. Thanks for the update. The Eclipse Update component is no longer under development, and no longer exists in the Eclipse Platform 4.x stream. If this problem still occurs in Eclipse Platform 4.2 or later, please enter a new bug report against Equinox p2. |