Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-34662

cannot easily determine how many repos are started or finished rebuilding in create.browse.nodes task log


    • Notability:


      1. Start a create.browse.nodes task against All Repositories.
      2. This task can take a long time to complete with many or large repos.
      3. Try to examine the task specific log to determine how many repos have been rebuilt compared to the actual number of repos selected to rebuild. This is not possible with current logging.

      For each repo that is processed by this task you can see at minimum three main log lines

      2022-08-14 00:20:14,536+0000 INFO  [quartz-10-thread-14]  *SYSTEM org.sonatype.nexus.repository.content.browse.BrowseFacetImpl - Deleting browse nodes for repository jitpack.io
      2022-08-14 00:20:14,537+0000 INFO  [quartz-10-thread-14]  *SYSTEM org.sonatype.nexus.repository.content.browse.BrowseFacetImpl - Rebuilding browse nodes for repository jitpack.io
      2022-08-14 00:20:14,959+0000 INFO  [quartz-10-thread-14]  *SYSTEM org.sonatype.nexus.repository.content.browse.BrowseFacetImpl - Processed 87 / 87 jitpack.io assets in 419 ms

      From these log lines one can learn a few things but not THE answer to the question - at least not in a way that can easily grepped.

      The message "Processed 87 / 87 jitpack.io assets in 419 ms" is useful, but omits a keyword like "finished" that indicates it is done ( implied by the "processed" count ).

      The message "Rebuilding browse nodes for repository jitpack.io" suggest that rebuilding that repo has "started" but in truth it really HAS NOT based on other logs I have observed.

      Why is this important?

      Until a repo is fully built, the UI renders partial results confusing end users and no person can easily tell progress of the task and if that could explain why the component cannot be seen. Also trying to gauge when the task will finish all repos is near impossible, preventing adding an estimated timeline to address what could be another type of problem with the missing component.


      When a repo has completed or started having its browse nodes being rebuilt ( actually rebuilt, not only put in some queue ), then put a log message in the task log that can be uniquely grepped that demarcates that fact. Also include log line(s) that state how many repos have been rebuilt so far, out of some total number being processed.

      The end result should be one can use grep on a task log at default log levels to answer:

      • how many repos are rebuilt so far out of how many
      • what repos were rebuilt so far




            Unassigned Unassigned
            plynch Peter Lynch
            Last Updated By:
            Michael Oliverio Michael Oliverio
            0 Vote for this issue
            3 Start watching this issue