You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Benjamin Bentmann <be...@udo.edu> on 2008/08/01 12:55:09 UTC
Latency of syncs in Nexus with central
Hi,
does the Nexus instance serving our Hudson have a certain latency with
regard to catching up with central? I am wondering since CI failed [0]
on maven-invoker which I updated to use the just released
plexus-utils:1.5.6 [1]
Benjamin
[0]
https://ci.sonatype.org/job/maven-shared/185/org.apache.maven.shared$maven-invoker/console
[1] http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.5.6/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Latency of syncs in Nexus with central
Posted by Benjamin Bentmann <be...@udo.edu>.
Tamás Cservenák wrote:
> Central is _not_ proxied by Nexus, but is rsynced from repo1.maven.org
> to repository.sonatype.org, and it is served from there by Nexus as
> "hosted" repo. The problem is probably our rsync process (not [yet]
> fired, or something).
>
> Not that this solves your failed build, just explaining what happens
> "behind the curtains" :)
Thanks a lot, just what I wanted to know! I previously assumed it would
act like a web proxy but now I know better.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Latency of syncs in Nexus with central
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
This is more likely a problem in the local repo for that build. The fix is to wait until the other builds, complete and then run the purge local repo job to flush it. Then the new build should find it.
-----Original Message-----
From: Benjamin Bentmann [mailto:benjamin.bentmann@udo.edu]
Sent: Friday, August 01, 2008 2:54 PM
To: Maven Developers List
Subject: Re: Latency of syncs in Nexus with central
Brian E. Fox wrote:
>> Yep, I checked the crontab, it's actually running at 12:05 (CST) daily. I'll still add the proxy.
>
> Yep, it's all set now. The intent was to minimize traffic over to central since we had the mirror, but we can do both and it won't hurt anything.
Hm, is the proxy setup really working? The build still doesn't get the
artifact from central (just a few minutes ago):
https://ci.sonatype.org/job/maven-shared/188/org.apache.maven.shared$maven-invoker/console
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Latency of syncs in Nexus with central
Posted by Benjamin Bentmann <be...@udo.edu>.
Brian E. Fox wrote:
>> Yep, I checked the crontab, it's actually running at 12:05 (CST) daily. I'll still add the proxy.
>
> Yep, it's all set now. The intent was to minimize traffic over to central since we had the mirror, but we can do both and it won't hurt anything.
Hm, is the proxy setup really working? The build still doesn't get the
artifact from central (just a few minutes ago):
https://ci.sonatype.org/job/maven-shared/188/org.apache.maven.shared$maven-invoker/console
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Latency of syncs in Nexus with central
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Yep, it's all set now. The intent was to minimize traffic over to central since we had the mirror, but we can do both and it won't hurt anything.
-----Original Message-----
From: Benjamin Bentmann [mailto:benjamin.bentmann@udo.edu]
Sent: Friday, August 01, 2008 11:18 AM
To: Maven Developers List
Subject: Re: Latency of syncs in Nexus with central
Brian E. Fox wrote:
> Yep, I checked the crontab, it's actually running at 12:05 (CST) daily. I'll still add the proxy.
OK, waiting a day (at most) isn't a major issue, not much things are
that urgent that a commit can't wait, you only need to know. But if
Hudson gets a real-time proxy to central, well, I won't say no ;-)
Thanks, Brian.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Latency of syncs in Nexus with central
Posted by Benjamin Bentmann <be...@udo.edu>.
Brian E. Fox wrote:
> Yep, I checked the crontab, it's actually running at 12:05 (CST) daily. I'll still add the proxy.
OK, waiting a day (at most) isn't a major issue, not much things are
that urgent that a commit can't wait, you only need to know. But if
Hudson gets a real-time proxy to central, well, I won't say no ;-)
Thanks, Brian.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Latency of syncs in Nexus with central
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Yep, I checked the crontab, it's actually running at 12:05 (CST) daily. I'll still add the proxy.
-----Original Message-----
From: t.cservenak@gmail.com [mailto:t.cservenak@gmail.com] On Behalf Of Tamás Cservenák
Sent: Friday, August 01, 2008 11:03 AM
To: Maven Developers List
Subject: Re: Latency of syncs in Nexus with central
Hi there,
The problem is more how is central repo in public group on our Nexus served:
Central is _not_ proxied by Nexus, but is rsynced from repo1.maven.org
to repository.sonatype.org, and it is served from there by Nexus as
"hosted" repo. The problem is probably our rsync process (not [yet]
fired, or something).
Also, according logs, you points to at Hudson, shows that the 1.5.6
pom was there, but the jar was not. Hence, i think it is 99% the
rsync.
Not that this solves your failed build, just explaining what happens
"behind the curtains" :)
~t~
On Fri, Aug 1, 2008 at 12:55 PM, Benjamin Bentmann
<be...@udo.edu> wrote:
> Hi,
>
> does the Nexus instance serving our Hudson have a certain latency with
> regard to catching up with central? I am wondering since CI failed [0] on
> maven-invoker which I updated to use the just released plexus-utils:1.5.6
> [1]
>
>
> Benjamin
>
>
> [0]
> https://ci.sonatype.org/job/maven-shared/185/org.apache.maven.shared$maven-invoker/console
> [1] http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.5.6/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Thanks,
~t~
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Latency of syncs in Nexus with central
Posted by Tamás Cservenák <ta...@cservenak.net>.
Hi there,
The problem is more how is central repo in public group on our Nexus served:
Central is _not_ proxied by Nexus, but is rsynced from repo1.maven.org
to repository.sonatype.org, and it is served from there by Nexus as
"hosted" repo. The problem is probably our rsync process (not [yet]
fired, or something).
Also, according logs, you points to at Hudson, shows that the 1.5.6
pom was there, but the jar was not. Hence, i think it is 99% the
rsync.
Not that this solves your failed build, just explaining what happens
"behind the curtains" :)
~t~
On Fri, Aug 1, 2008 at 12:55 PM, Benjamin Bentmann
<be...@udo.edu> wrote:
> Hi,
>
> does the Nexus instance serving our Hudson have a certain latency with
> regard to catching up with central? I am wondering since CI failed [0] on
> maven-invoker which I updated to use the just released plexus-utils:1.5.6
> [1]
>
>
> Benjamin
>
>
> [0]
> https://ci.sonatype.org/job/maven-shared/185/org.apache.maven.shared$maven-invoker/console
> [1] http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.5.6/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Thanks,
~t~
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Latency of syncs in Nexus with central
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
It's once a week, but I'll add a proxy of central back to handle these
timing issues. (it will be lower in the group so that the mirror is
consulted first)
-----Original Message-----
From: Benjamin Bentmann [mailto:benjamin.bentmann@udo.edu]
Sent: Friday, August 01, 2008 6:55 AM
To: Maven Developer List
Subject: Latency of syncs in Nexus with central
Hi,
does the Nexus instance serving our Hudson have a certain latency with
regard to catching up with central? I am wondering since CI failed [0]
on maven-invoker which I updated to use the just released
plexus-utils:1.5.6 [1]
Benjamin
[0]
https://ci.sonatype.org/job/maven-shared/185/org.apache.maven.shared$mav
en-invoker/console
[1]
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.5.6/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org