We had our Jira 5.1.6 instance configured to use a customised path for our indexes. It was set to a path of /ramdisk_mount/lucene
A new user with Jira system administrator access who was looking around the administration interface clicked the radio button for "Use Default Directory" and pressed the "Re-Index" button.
We know we can't change back via the UI to /ramdisk_mount/lucene
Can we change back by the following steps or something similar?
1. Shutdown Jira
2. Update a record in the database (we use MySQL 5.x) to set the custom path for indexes (I would need instruction on tables etc)
3. Copy the index files from the new location to the old location
4. Start Jira
After choosing the default directory for index path, I am afraid that we are no longer able to switch the index directory to use custom path again. This information is outlined in the following documentation:
Choosing a custom Index Path:
Therefore, I may confirm that it's not possible for us to use the custom path from JIRA UI.
As for updating the records in database, supposedly the index path information are stored in the propertyentry, and propertystring table. However, I am unable to confirm if updating the record will work, since I was unable to change the attachment path directly from the database. There's a KB article written to change the attachment path, but it seemed not be working for me, hence I couldn't confirm the same for index path:
Another alternative for us here is to use symlink instead, to link the $JIRA_HOME/caches directory to /ramdisk_mount/lucene.
Though it's not much, but I hope that the info above helps.
select * from propertyentry where propertyentry.PROPERTY_KEY like '%index%'
this will get you the property IDs of the indexing attributes, specifically the jira.option.indexing (make sure this is set to 1) and also jira.path.index.
You can then update the propertynumber and propertystring tables respectively with the value you want.
This is the method I had to use when migrating to another server and the indexing location changed.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs