Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-17784

New node_props index fails on creation which causes Artifactory to run without any index

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 6.5.0, 6.5.1, 6.5.2
    • Fix Version/s: 6.5.3
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Leap 34

      Description

      This was triggered by RTFACT-17337.
      The way RTFACT-17337 was implemented is that during an upgrade to 6.5.0 we are dropping the old index and creating a new index.
      In case the new index' creation is failing, the upgrade proceeds and Artifactory runs without an index on the properties table, which causes constant full scans.

      We should not get into a state where there is no index at all, and in case the creation of new index is failing we should at least re-create the new index.

      Once above is fixed, we should update the REST API:
      https://www.jfrog.com/confluence/display/RTF/Troubleshooting#Troubleshooting-RecoveringfromError:AnincompatibleindexhasbeenfoundfortheArtifactory%E2%80%98node_props%E2%80%99databasetable

      So this REST will start by dropping the old index, cutting the properties to 2400 chars, and creating the new improved index.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                yoazm Yoaz Menda (Inactive)
                Reporter:
                arielk Ariel Kabov
                Assigned QA:
                Alex Dvorkin
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: