How to set up auto re-index in Jira

Hi,

I'm relatively new to Confluence / Jira and i've been struggling to set up auto re-indexing of Jira. I was told by Confluence support to download the Confluence Command Line Interface plugin but haven't a clue how to implement this tool in CentOS. Isn't there perhaps a layman's how-to manual to show me the way? My background is Microsoft so...enough said :)

Regards

4 answers

1 accepted

Hi there,

There are so many customers enquiring about auto-indexing, why doesn't Atlassian just build their new Jira releases with auto-indexing built in?

Regards

There aren't actually many asking about it.

Having to re-index the whole system is unusual, and thinking "we should do this regularly" is simply patching over a problem you should really be trying to fix the root cause of.

However, any changes done to the plugins require you to perform a re-index on the machine which is not that practical when you have to perform the re-index when the employees leave the office. Performing a background index will decrease the perofrmance on the system... so that is not an option.

Correct, but adding an add-on that requires indexing should be something considered as system maintenance, and the indexing should be done manually by an admin when it is required and the users agree to the downtime.  Not regular indexing.

Hi Nic,

Thanks so much for getting back to me even though this is quite an old thread:) I am an administrator myself and I am currently searching for a good tool that can perform this auto re-indexing on our JIRA machine. Our machine is hosted on a Centos Server and running 2 applications both JIRA & Confluence. Do you know of any methods to perform an auto re-index 1 a month for example or every 2 weeks? This can save us a lot of time and also will be very useful when changes are done on our Live System. Performing a re-index because of changes done on the Live system will be done automatically without having to stay here and do a manual re-index. What would you suggest?smile
Thanks very much for your time

Regards

Matt

You've missed the point.  A desire to do regular re-indexing is indicative of a deeper fault that you need to fix instead of patch over.

If you need to re-index because of config changes, they should be booked with the business and done manually.

Hi Nic,

I got your point.... but my point is I WANT to perform an automatic re-index every 2 weeks as we do regular changes in the plugins and workflows very regular in our company. There is no indication of any deeper faults. We are NOT performing a re-index in our system because we have faults in our system which are fixed by a re-index... I don't know whether I am answering your above statement. Instead of performing a manual re-index every 2 weeks because of config changes I would like to install something which can do this re-index automatically during a weekend. Is this possible or not?

Thanks

 

Matt

Ok, so you've got half the point - you are not re-indexing to patch over a problem.

So, the other reason for re-indexing is config change.  That should be done when the configuration has been changed.  Not 2 weeks later.  You should make the changes and re-index as soon as possible.  Not on a schedule.

2 votes

From JIRA 6.1 onwards, it is possible to trigger a re-index via the REST API:

https://docs.atlassian.com/jira/REST/6.1/#d2e3239

Hi,

I know that this is an old thread.

Just meaning to ask if it would be wise to trigger a scheduled re-index, via a cronjob as you have stated here.

My JIRA instance is of version 6.4.4 at the moment.

I have checked that the using the REST API has some caused some bugs, for example

Would it be better to trigger the re-index from the JIRA UI instead of through the REST API?.

Thanks,

Hi Alfie,

Although it is possible to schedule a period re-index, this operation should only be triggered when necessary (e.g. after changes that require a re-index).

The bug JRASERVER-63284 only affects Data Center installations.

Taking that into consideration, if you're running a Data Center version of JIRA, we'd recommend you to trigger the re-index via the UI instead. Otherwise, if you're on JIRA Software Server, either option should be fine.

Cheers

Hi Danilo,

Thank you for the reply, even though this is an old thread.

I understand, i will take note of what you have said.

Thank you

 

 

0 votes

CLI is a commmand line interface. You will find lot of info, including installation, usage etc, here: https://bobswift.atlassian.net/wiki/display/JCLI/JIRA+Command+Line+Interface

On CentOS, you have shell script that you can run.

Thank you kindly sir :)

I've come across this post but what do i do with it? Obviously i have to add this to a file and point CLI to it. There isn't really set by step instruction to set this up:

https://confluence.atlassian.com/display/JIRACOM/Automating+JIRA+operations+via+wget?focusedCommentId=229839497#comment-229839497

You're getting confused.

The CLI is for making the remote functions easier to use when you're scripting outside.

The script you have found is a script for the sh shell. It's nothing to do with the CLI, you just run it on a Unix box. The "curl" command may need to be added, but all it does is log into Jira and click the "re index" button for you, without a browser.

They both hit Jira remotely (you can run them on any machine that can talk to your Jira), and they don't need a browser. But they're different methods.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,801 views 11 18
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot