[MDEV-8651] this repository is so slow Created: 2015-08-19 Updated: 2016-02-11 Resolved: 2016-02-11 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Packaging |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Critical |
| Reporter: | Aurélien LEQUOY | Assignee: | Daniel Bartholomew |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Any idea, to make it better, or have an other one with same package ? (without make my own repo) I have to upgrade 100 servers and it's really a problem. |
| Comments |
| Comment by Daniel Bartholomew [ 2015-10-30 ] | |||||
|
Which repository are you talking about? Is it yum.mariadb.org? If so there might be something you can do. The yum repositories on yum.mariadb.org are replicated on our mirror network. So, for example, you could change your mariadb.repo files to something similar to the following to use the osuosl mirror instead of yum.mariadb.org (I'm using rhel7-amd64 and MariaDB 10.0 in the example, change to whatever yum-based distro and MariaDB version you are using) :
| |||||
| Comment by Aurélien LEQUOY [ 2015-10-30 ] | |||||
|
It was about repo for Debian. (I saw it). Was speaking with friend he updated to MariaDB 10.0.22 to test ClusterControl with and first and second : OK. Last one error 404. | |||||
| Comment by Daniel Bartholomew [ 2015-10-30 ] | |||||
|
Do you know which MariaDB mirror you are using for your Debian repository? If you go to the Repository Configuration Tool https://downloads.mariadb.org/mariadb/repositories/ and configure an example Debian repo, you can switch the mirror chosen for you to a different one. We don't have a way to increase the bandwidth of a given mirror, but we have quite a few of them spread around the world, so you should be able to find one that works better than the one you are currently using. When configuring an example repository for Debian the repository configuration tool will only give you a choice of five or so nearby mirrors (based on geo-location) but there is a "Show all Mirrors" button that will give you the full list. | |||||
| Comment by Aurélien LEQUOY [ 2015-10-30 ] | |||||
|
i tried any different and same problem (no example now), try to DL : http://archive.mariadb.org/mariadb-10.0.21/bintar-linux-x86_64/mariadb-10.0.21-linux-x86_64.tar.gz | |||||
| Comment by Daniel Bartholomew [ 2015-10-30 ] | |||||
|
Ok, so you're not using a repository, you're downloading a bintar. You really do not want to use the archive.mariadb.org mirror. It is a historical archive of all MariaDB releases and is bandwidth-limited. A standard mirror will serve you much better. For example, the MariaDB 10.0.21 Linux x86_64 bintar from the OSUOSL mirror: ...or the recently released 10.0.22: When you're on downloads.mariadb.org looking at a release you can change the mirror by scrolling down to the "Mirror" section in the right-side column, clicking on a different mirror, and waiting for the page to refresh. | |||||
| Comment by Aurélien LEQUOY [ 2015-11-12 ] | |||||
|
I updated some servers 5~10 then : yum install MariaDB-server MariaDB-client got same problem with apt | |||||
| Comment by Daniel Bartholomew [ 2015-11-12 ] | |||||
|
Aurelien_LEQUOY: I'm able to successfully load http://yum.mariadb.org/10.0/centos6-amd64/repodata/repomd.xml (I tried just now) so I don't know why you're seeing the "Couldn't resolve..." error. You could try using the alternative mariadb.repo file I pasted above comment-77458, modified for rhel6-amd64. For APT, it's impossible you're seeing the same error as there are no APT repositories on yum.mariadb.org. What is your actual error with APT? Thanks. | |||||
| Comment by Aurélien LEQUOY [ 2015-11-12 ] | |||||
|
no i got 404 for APT | |||||
| Comment by Daniel Bartholomew [ 2015-11-12 ] | |||||
|
But to what repository? It's definitely not the yum.mariadb.org repository. | |||||
| Comment by Daniel Bartholomew [ 2016-02-11 ] | |||||
|
yum.mariadb.org is now load-balanced across 4 different hosts, so it should be much faster Unable to fix the APT 404 issue as I don't know which mirror was configured, so closing. |