Having a stale index directory causes some logging weirdness.

XMLWordPrintable

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      • Having a stale index directory causes some weirdness.
        1. Start up JIRA.
        2. Configure JIRA.
        3. Stop JIRA. Make the index directory readonly (I make the caches directory in JIRA_HOME read only)
        4. Restart JIRA. JIRA does not complain about the directory being invalid until you actually try to do some searching. Should be issue some warnings before hand?
        5. Goto the "Admin > Indexing". Note that indexing appears to be disabled.
        6. Reindex JIRA. I get the error message "Error occurred while activating indexes: com.atlassian.jira.util.RuntimeIOException: java.io.IOException: Cannot create directory: E:\blitz\home\caches\indexes\comments". I am then returned to the index screen and it appears that the index is now enabled even though it is broken.
        7. Try to reindex again. This time I get a long runnin task result with stack trace like the following. Indexing still appears to be enabled. 
          com.atlassian.jira.util.RuntimeIOException: java.io.IOException: Cannot create directory: E:\blitz\home\caches\indexes\comments
	at com.atlassian.jira.issue.index.IndexDirectoryFactory$Name.getFileSystemDirectory(IndexDirectoryFactory.java:91)
	at com.atlassian.jira.issue.index.IndexDirectoryFactory$Name.getDirectory(IndexDirectoryFactory.java:78)
	at com.atlassian.jira.issue.index.IndexDirectoryFactory$IndexPathAdapter.get(IndexDirectoryFactory.java:125)
	at com.atlassian.jira.issue.index.IndexDirectoryFactory$IndexPathAdapter.get(IndexDirectoryFactory.java:107)
	at com.atlassian.jira.issue.index.DefaultIssueIndexer$Lifecycle.open(DefaultIssueIndexer.java:285)
	at com.atlassian.jira.issue.index.DefaultIssueIndexer$Lifecycle.iterator(DefaultIssueIndexer.java:264)
	at com.atlassian.jira.issue.index.DefaultIssueIndexer.deleteIndexes(DefaultIssueIndexer.java:173)
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexAll(DefaultIndexManager.java:225)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:71)
	at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28)
	at $Proxy9.reIndexAll(Unknown Source)
	at com.atlassian.jira.util.index.IndexLifecycleManager$Composite.reIndexAll(IndexLifecycleManager.java:112)
	at com.atlassian.jira.web.action.admin.index.ReIndexAsyncIndexerCommand.doReindex(ReIndexAsyncIndexerCommand.java:29)
	at com.atlassian.jira.web.action.admin.index.AbstractAsyncIndexerCommand.call(AbstractAsyncIndexerCommand.java:55)
	at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:360)
	at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
	at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
	at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:178)
	at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:252)
	at java.lang.Thread.run(Thread.java:619)

            Assignee:
            Unassigned
            Reporter:
            bain
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: