You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repo-maintainers@maven.apache.org by "Brian E. Fox" <br...@reply.infinity.nu> on 2008/12/12 18:09:03 UTC
More index troubles (q4e this time)
It came to my attention this morning that Q4e doesn't check the
timestamp on the index or use the api and thus downloads the index on
every restart. Worse than the Artifactory issue where it wasn't known,
this issue was reported back in June:
http://code.google.com/p/q4e/issues/detail?id=465 It goes without saying
that this is not in the best interest of the repository community. We're
looking into ways to minimize the damage and cost from this and I hope
that team takes extra-ordinary measures to fix and distribute an update
as Artifactory did.
--Brian
Re: More index troubles (q4e this time)
Posted by Carlos Sanchez <ca...@apache.org>.
Back in June it wasn't confirmed, and unable to reproduce it.
Maybe at that time it was caused by an user proxy messing with the
headers. Now it definitely seems to affect more people, Nginx or not,
I don't know, but the if-modified-since is being sent.
Anyway, I expect it to be fixed pretty soon.
On Fri, Dec 12, 2008 at 11:37 AM, Brian E. Fox <br...@reply.infinity.nu> wrote:
> Joakim, that's good to know that it's not _every_ time, just the first
> time you touch a pom after restarting. This could still be a large
> amount of downloads repeatedly by individual users. The main concern is
> that this seems to have been known since June. Nginx wasn't in place
> until October so it's not possible that this was the cause the whole tim
>
> -----Original Message-----
> From: Joakim Erdfelt [mailto:joakim@erdfelt.com]
> Sent: Friday, December 12, 2008 2:30 PM
> To: repo-maintainers@maven.apache.org
> Cc: Maven Project Management Committee List
> Subject: Re: More index troubles (q4e this time)
>
> Saying that the index is pulled every time eclipse is restarted is
> inaccurate.
>
> Code to pull index is trigged on indexer plugin activation.
> Indexer plugin activation occurs lazily.
> Indexer plugin activation occurs, for example, when pom is about to be
> modified.
> Indexer plugin updates the index once per eclipse session, by sending a
> request with the If-Modified-Since header.
>
> I have repo1.maven.org set to 192.168.1.131 (in /etc/hosts) on all of my
>
> dev machines for the past week (Since Dec 8).
> Since I rarely modified the pom on a project this week, i only had 2
> requests for the index show up in my Apache httpd logs on my
> 192.168.1.131 box all week.
>
> I have also started and stopped Eclipse instances with Q4E installed
> hundreds of times this week (running Plug-in JUnit tests with full
> eclipse workspace startup).
>
> -joakime
>
> Carlos Sanchez wrote:
>> we are working on it see
>> http://code.google.com/p/q4e/issues/detail?id=465
>>
>> the if-modified-since is being used but for some reason everytime
>> eclipse is restarted it may pull the index again, although only once
>> per restart, index is not retrieved after that.
>>
>>
>> On Fri, Dec 12, 2008 at 11:09 AM, Brian E. Fox
> <br...@reply.infinity.nu> wrote:
>>
>>> Part of this problem seems to be how Nginx handles the
>>> If-Modified-Since. It does an exact match and that's all. Fortunately
> S3
>>> does handle it correctly, so my previous suggestion to use redirects
> to
>>> S3 for the index would help mitigate these problems. It appears that
>>> Abel is also working on a patch.
>>>
>>>
>>>
>>> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
>>> Sent: Friday, December 12, 2008 12:09 PM
>>> To: repo-maintainers@maven.apache.org
>>> Cc: Maven Project Management Committee List
>>> Subject: More index troubles (q4e this time)
>>>
>>>
>>>
>>> It came to my attention this morning that Q4e doesn't check the
>>> timestamp on the index or use the api and thus downloads the index on
>>> every restart. Worse than the Artifactory issue where it wasn't
> known,
>>> this issue was reported back in June:
>>> http://code.google.com/p/q4e/issues/detail?id=465 It goes without
> saying
>>> that this is not in the best interest of the repository community.
> We're
>>> looking into ways to minimize the damage and cost from this and I
> hope
>>> that team takes extra-ordinary measures to fix and distribute an
> update
>>> as Artifactory did.
>>>
>>>
>>>
>>> --Brian
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
RE: More index troubles (q4e this time)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Joakim, that's good to know that it's not _every_ time, just the first
time you touch a pom after restarting. This could still be a large
amount of downloads repeatedly by individual users. The main concern is
that this seems to have been known since June. Nginx wasn't in place
until October so it's not possible that this was the cause the whole tim
-----Original Message-----
From: Joakim Erdfelt [mailto:joakim@erdfelt.com]
Sent: Friday, December 12, 2008 2:30 PM
To: repo-maintainers@maven.apache.org
Cc: Maven Project Management Committee List
Subject: Re: More index troubles (q4e this time)
Saying that the index is pulled every time eclipse is restarted is
inaccurate.
Code to pull index is trigged on indexer plugin activation.
Indexer plugin activation occurs lazily.
Indexer plugin activation occurs, for example, when pom is about to be
modified.
Indexer plugin updates the index once per eclipse session, by sending a
request with the If-Modified-Since header.
I have repo1.maven.org set to 192.168.1.131 (in /etc/hosts) on all of my
dev machines for the past week (Since Dec 8).
Since I rarely modified the pom on a project this week, i only had 2
requests for the index show up in my Apache httpd logs on my
192.168.1.131 box all week.
I have also started and stopped Eclipse instances with Q4E installed
hundreds of times this week (running Plug-in JUnit tests with full
eclipse workspace startup).
-joakime
Carlos Sanchez wrote:
> we are working on it see
> http://code.google.com/p/q4e/issues/detail?id=465
>
> the if-modified-since is being used but for some reason everytime
> eclipse is restarted it may pull the index again, although only once
> per restart, index is not retrieved after that.
>
>
> On Fri, Dec 12, 2008 at 11:09 AM, Brian E. Fox
<br...@reply.infinity.nu> wrote:
>
>> Part of this problem seems to be how Nginx handles the
>> If-Modified-Since. It does an exact match and that's all. Fortunately
S3
>> does handle it correctly, so my previous suggestion to use redirects
to
>> S3 for the index would help mitigate these problems. It appears that
>> Abel is also working on a patch.
>>
>>
>>
>> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
>> Sent: Friday, December 12, 2008 12:09 PM
>> To: repo-maintainers@maven.apache.org
>> Cc: Maven Project Management Committee List
>> Subject: More index troubles (q4e this time)
>>
>>
>>
>> It came to my attention this morning that Q4e doesn't check the
>> timestamp on the index or use the api and thus downloads the index on
>> every restart. Worse than the Artifactory issue where it wasn't
known,
>> this issue was reported back in June:
>> http://code.google.com/p/q4e/issues/detail?id=465 It goes without
saying
>> that this is not in the best interest of the repository community.
We're
>> looking into ways to minimize the damage and cost from this and I
hope
>> that team takes extra-ordinary measures to fix and distribute an
update
>> as Artifactory did.
>>
>>
>>
>> --Brian
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
Re: More index troubles (q4e this time)
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
Saying that the index is pulled every time eclipse is restarted is
inaccurate.
Code to pull index is trigged on indexer plugin activation.
Indexer plugin activation occurs lazily.
Indexer plugin activation occurs, for example, when pom is about to be
modified.
Indexer plugin updates the index once per eclipse session, by sending a
request with the If-Modified-Since header.
I have repo1.maven.org set to 192.168.1.131 (in /etc/hosts) on all of my
dev machines for the past week (Since Dec 8).
Since I rarely modified the pom on a project this week, i only had 2
requests for the index show up in my Apache httpd logs on my
192.168.1.131 box all week.
I have also started and stopped Eclipse instances with Q4E installed
hundreds of times this week (running Plug-in JUnit tests with full
eclipse workspace startup).
-joakime
Carlos Sanchez wrote:
> we are working on it see
> http://code.google.com/p/q4e/issues/detail?id=465
>
> the if-modified-since is being used but for some reason everytime
> eclipse is restarted it may pull the index again, although only once
> per restart, index is not retrieved after that.
>
>
> On Fri, Dec 12, 2008 at 11:09 AM, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
>> Part of this problem seems to be how Nginx handles the
>> If-Modified-Since. It does an exact match and that's all. Fortunately S3
>> does handle it correctly, so my previous suggestion to use redirects to
>> S3 for the index would help mitigate these problems. It appears that
>> Abel is also working on a patch.
>>
>>
>>
>> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
>> Sent: Friday, December 12, 2008 12:09 PM
>> To: repo-maintainers@maven.apache.org
>> Cc: Maven Project Management Committee List
>> Subject: More index troubles (q4e this time)
>>
>>
>>
>> It came to my attention this morning that Q4e doesn't check the
>> timestamp on the index or use the api and thus downloads the index on
>> every restart. Worse than the Artifactory issue where it wasn't known,
>> this issue was reported back in June:
>> http://code.google.com/p/q4e/issues/detail?id=465 It goes without saying
>> that this is not in the best interest of the repository community. We're
>> looking into ways to minimize the damage and cost from this and I hope
>> that team takes extra-ordinary measures to fix and distribute an update
>> as Artifactory did.
>>
>>
>>
>> --Brian
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
Re: More index troubles (q4e this time)
Posted by Carlos Sanchez <ca...@apache.org>.
we are working on it see
http://code.google.com/p/q4e/issues/detail?id=465
the if-modified-since is being used but for some reason everytime
eclipse is restarted it may pull the index again, although only once
per restart, index is not retrieved after that.
On Fri, Dec 12, 2008 at 11:09 AM, Brian E. Fox <br...@reply.infinity.nu> wrote:
> Part of this problem seems to be how Nginx handles the
> If-Modified-Since. It does an exact match and that's all. Fortunately S3
> does handle it correctly, so my previous suggestion to use redirects to
> S3 for the index would help mitigate these problems. It appears that
> Abel is also working on a patch.
>
>
>
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Friday, December 12, 2008 12:09 PM
> To: repo-maintainers@maven.apache.org
> Cc: Maven Project Management Committee List
> Subject: More index troubles (q4e this time)
>
>
>
> It came to my attention this morning that Q4e doesn't check the
> timestamp on the index or use the api and thus downloads the index on
> every restart. Worse than the Artifactory issue where it wasn't known,
> this issue was reported back in June:
> http://code.google.com/p/q4e/issues/detail?id=465 It goes without saying
> that this is not in the best interest of the repository community. We're
> looking into ways to minimize the damage and cost from this and I hope
> that team takes extra-ordinary measures to fix and distribute an update
> as Artifactory did.
>
>
>
> --Brian
>
>
>
>
>
>
>
>
>
>
RE: More index troubles (q4e this time)
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Part of this problem seems to be how Nginx handles the
If-Modified-Since. It does an exact match and that's all. Fortunately S3
does handle it correctly, so my previous suggestion to use redirects to
S3 for the index would help mitigate these problems. It appears that
Abel is also working on a patch.
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Friday, December 12, 2008 12:09 PM
To: repo-maintainers@maven.apache.org
Cc: Maven Project Management Committee List
Subject: More index troubles (q4e this time)
It came to my attention this morning that Q4e doesn't check the
timestamp on the index or use the api and thus downloads the index on
every restart. Worse than the Artifactory issue where it wasn't known,
this issue was reported back in June:
http://code.google.com/p/q4e/issues/detail?id=465 It goes without saying
that this is not in the best interest of the repository community. We're
looking into ways to minimize the damage and cost from this and I hope
that team takes extra-ordinary measures to fix and distribute an update
as Artifactory did.
--Brian