thanks for investigating, this sounds like a plausible explanation. NB 19 will disable remote repo indexing in out-of-space situations and won't try it again until enabled by the user (checkbox in maven indexing settings).

index footprint is also almost cut in half and can be further decreased by enabling filters in the settings. Some users have also restricted tmp space, which is why extraction will go directly into the cache folder.

this is all testable in dev builds,

best regards,
michael

On 12.06.23 21:32, Peter Hull wrote:
I found only three log files all from Friday but it showed I was running out of disk space, hence the indexing was never done. (My laptop has a small system drive and a bigger data drive, it’s a constant struggle to keep free space on the former). This might be the cause of my problem.


On Mon, 12 Jun 2023 at 10:56, Michael Bien <mbie...@gmail.com> wrote:

    On 12.06.23 09:51, Peter Hull wrote:
    > On Sun, 11 Jun 2023 at 19:05, Tamás Cservenák
    <ta...@cservenak.net> wrote:
    >> The central index last publish happened on 5th June 2023.
    > Thanks everyone for the comments.
    >
    > I've not been monitoring it specifically but I had the feeling that
    > indexer was running more frequently, that's why I asked if there
    was a
    > log so I could confirm it (or not!)

    I forgot to answer this - sorry, check for:

    INFO [org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl]:
    Indexing of [repo_name] took [time]s

    logger is enabled by default, time includes download.

    you can also see the last update timestamp in:

    
[netbeans_config_folder]/18/config/Preferences/org/netbeans/modules/maven/repositories/[repo_name].properties

    which is set on every index update.


    > I believe it was indexing rather than just an update check,
    because it
    > makes my laptop fans spin up for a few minutes.
    > I have only recently upgraded to NB18 so for example if I had done
    > that on 4th June I would have had an indexer run on that day and
    again
    > the following day, is that correct?

    This shouldn't happen due to the min update interval which is 7
    days by
    default. But I can take another look at the code.


    >   And also, if I had closed NB
    > before the indexing had finished, would it start again from scratch,
    > or does it work incrementally?

    It would start again from scratch if it is cancelled by the user (e.g
    due to shutdown).


    >
    > I'll keep an eye on it and let you know if it seems to be
    running more
    > frequently than updates to the
    nexus-maven-repository-index.properties
    > would suggest.

    great, thanks!

    you could also give a NB 19 dev build a try if you want since it has
    many maven-indexer improvements already merged:

    
https://ci-builds.apache.org/job/Netbeans/job/netbeans-linux/lastSuccessfulBuild/artifact/nbbuild/


    best regards,

    -mbien


    >
    > Pete
    >
    >
    ---------------------------------------------------------------------
    > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
    > For additional commands, e-mail: dev-h...@netbeans.apache.org
    >
    > For further information about the NetBeans mailing lists, visit:
    > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
    >
    >
    >

Reply via email to