nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can we disable scriptrunner while background indexing is ongoing?

sachin gangam_dxlrg8

Our indexes were corrupt and we are in process of rebuilding our indexes (we deleted indexes, cache from jira-home) and we see that only 20k issues have reindexed (in 5hours) out of 1015221 issues. Currently our instance is up and users are able to create issues. However, we cannot see issues on the boards, dashboards, or in issue navigator. And, we think that indexing is going to take 15-17hours to complete.

From my previous experience I know that scripted fields make the whole indexing processing slow and I would like to know what steps we can take to speed up the process. All of our 10k users are affected right now and we would like to know and understand what would be the right measures to take to resolve this issue.

We have 50+ scripted fields and the reindexing is going on for 5hours now. Can we disable scriptrunner while background indexing is ongoing?

Thank you for the help.

Accepted answers

Nic Brough -Adaptavist-

Technically, you can turn it off while re-indexing.

But that will break every scripted field you've got. The indexing throws away the index for the field and re-creates it. If the scripted field script is not run during index, it won't create the data for the field.

You'll basically destroy all your scripted fields, and the only way to get them back is to run a full re-index with Scriptrunner enabled.

All comments

Nic Brough -Adaptavist-

Technically, you can turn it off while re-indexing.

You'll basically destroy all your scripted fields, and the only way to get them back is to run a full re-index with Scriptrunner enabled.

sachin gangam_dxlrg8

Thank you for prompt reply @Nic Brough -Adaptavist- . Some of the scripted fields are scoped to "all projects", how would it affect the indexing if I change the scope of these fields?

I also see that sometimes it takes 5hours to reindex 100issues and all of the sudden I see a big jump in few minutes (for example just now it took 5mins to reindex 1000issues), can you please tell me why you think this is happening?

sachin gangam_dxlrg8

Does changing "Searcher: Free Text Searcher " to "none" help fasten the current background indexing process?

Nic Brough -Adaptavist-

It will, a little.

It will also destroy your ability to search or sort on the field until you re-enable it and do a full re-index.

Disabling bits of it is not the answer here. If you turn off bits of the indexing, you reduce or destroy the usefulness of your scripted fields.

Before I write a long if/then essay, can you tell me what version of Jira you are on? Some versions index in very different ways.

Ryan Trondsen

I have noticed that during a full re-index, any scripted field that does a JQL query in the script will cause errors in the log, and will slow the re-index to never finish. We have to disable those fields before running the full re-index, and then re-enable those fields, and run a localized re-index on the issues that use those scripted fields. In general, scripted fields and BigPicture don't cause massive delays. We generally only run background re-indexes, and haven't had issues. Perhaps try disabling individual fields and testing your reindexing to see if a particular one is causing issues. I seriously doubt BigPicture is doing it.

Nic Brough -Adaptavist-

That smacks of very poor scripts, ones trying to do too much, or, more likey, recursing - what are they doing in the searches? Would the read of the results be calling another search which calls another search which calls another search....

Ryan Trondsen

When using the SearchService in a Scripted Field, it fails to re-index during a "Full" reindex only (ie when the index is deleted) as the script tries to search the index). An example function I use is this:

// Find issues method, use: findIssues("JQL Search here")
def findIssues(String jqlSearch) {
    def user = ComponentAccessor.jiraAuthenticationContext.loggedInUser
    def searchService = ComponentAccessor.getComponentOfType(SearchService)
    def parseResult = searchService.parseQuery(user, jqlSearch)
    if (!parseResult.isValid()) {
        return null
    }
    def results = searchService.search(user, parseResult.query, PagerFilter.unlimitedFilter)
    return results.results
}

I generally avoid using JQL search scripts in scripted fields whenever possible though.

Again, this is only during full re-indexes. We have 200k+ issues and have 2-3 hour max background re-indexes.

Nic Brough -Adaptavist-

Hmm. That would make some sense - the index call will cause a search which will fail because the index it's reading might not be there. Slightly recursive. However

1) It should just fail and leave the scripted field with a duff index, not massively slow down

2) On a small-medium system, I just tried it and got a handful of "can't read index" and a lot of "no results from search, so returning nothing" back.

I can't say anything about speed, it took 15 minutes before I added the script, 12 afterwards, but the number of issues the field is valid for isn't huge.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server