[RTFACT-17784] New node_props index fails on creation which causes Artifactory to run without any index Created: 06/Nov/18  Updated: 15/Nov/18  Resolved: 11/Nov/18

Status: Resolved
Project: Artifactory Binary Repository
Component/s: None
Affects Version/s: 6.5.0, 6.5.1, 6.5.2
Fix Version/s: 6.5.3

Type: Bug Priority: Critical
Reporter: Ariel Kabov Assignee: Yoaz Menda (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Trigger
was triggered by RTFACT-17337 Performance improvement: Create a mor... Resolved
Assigned QA: Alex Dvorkin
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.


Generated at Fri Dec 13 11:51:12 UTC 2019 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.