[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] tycho 0.11.0 always downloading content.xml and artifacts.xml from local p2 helios mirror
|
Hi Igor,
I do not wipe the local repository and I noticed that the data is cached locally in .m2/repository/cache/tycho/p2-repository-metadata.
I am using (still evaluating) Nexus Pro 1.9.1. It is configured like that:
Not Found Cache TTL: 1440 min
Artifact Max Age: -1 min
Metadata Max Age: 1440 min
The funny thing is that it already happened twice that it did not update the content.xml and artifacts.xml. So it has periods (of more than 10 builds) when it does update and when it does not. I do not understand what it depends on. Any ideas? Is it sensitive to the clock?
Thank you for the eclipse bug issue. In my case, the most time is spent downloading the content.xml and artifacts.xml.
I can also see that it does HEAD requests in my load balancer logs but also often followed by GETs:
--cut--
09:51:26 HEAD
09:59:31 HEAD
10:05:25 HEAD
10:05:26 GET
10:09:14 HEAD
10:11:52 HEAD
10:15:19 GET
10:16:59 HEAD
10:18:44 GET
10:21:19 HEAD
10:23:17 GET
10:28:59 HEAD
10:30:51 GET
10:32:17 HEAD
10:34:17 GET
10:35:15 HEAD
10:37:10 GET
10:38:34 HEAD
10:40:00 GET
10:40:12 HEAD
10:41:53 GET
10:42:29 HEAD
10:43:59 GET
10:52:30 HEAD
10:54:18 GET
10:55:31 HEAD
10:57:36 GET
10:59:43 HEAD
11:01:37 GET
11:31:42 HEAD
11:35:31 GET
11:51:19 HEAD
11:52:12 GET
11:52:14 HEAD
11:53:04 HEAD
11:55:44 GET
12:01:25 HEAD
15:06:28 HEAD
15:09:12 GET
15:17:26 HEAD
15:18:21 HEAD
15:23:58 HEAD
15:26:31 HEAD
16:22:57 HEAD
17:04:24 HEAD
--cut--
I assume since 15:17 it is not fetching the content.xml each time. before that it fetched it. Note that I have not changed anything the whole time.
Best regards,
Dimo
On Tue, May 3, 2011 at 1:17 PM, Igor Fedorenko
<ifedorenko@xxxxxxxxxxxx> wrote:
Tycho is expected to download remote p2 repository metadata once and
then only check for updates (which by itself can take long time, see [1]).
So unless you wipe local maven repository before each build, the
behaviour that you see appears to be a bug.
When version of Nexus is that? Assuming this is Nexus Pro with p2
support, do you know how often it is configured to check for remote p2
metadata updates (the parameter is called "Metadata Max Age" in p2 proxy
repo configuration UI).
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=337022
--
Regards,
Igor
_______________________________________________
