Skip to Content
author's profile photo Former Member
Former Member

Lucenesearch-RebuildIndex-Job and Lucenesearch-UpdateIndex-Job run for long time

Good evening, we're working on hybris (ex- novo installation on a new machine) with some customization on solr search providers and facets (hoping this details could help i the resolution of the issue).

During the monitoring phase of the project, we have been noticing that LuceneIndex Cronjobs ("Lucenesearch-RebuildIndex-Job" and "Lucenesearch-UpdateIndex-Job") run for very long time (in terms of hours or days sometimes) decreasing obviously the system performances.

Following our questions: 1) Is there a way to understand if these jobs can be deactivated? 2) Which is their purpose? 3) Could they affect /being affected solr search or indexing? 4) Why do they need all this time?

In the application log, we've found also:

03.02.2018 12:15:31: ERROR: Caught throwable error while accessing lucenesearch index hmc de.hybris.platform.lucenesearch.jalo.IndexAccessException: error while accessing lucenesearch index hmc[HY-0] at de.hybris.platform.lucenesearch.jalo.LuceneIndex.removeItemFromIndexImpl( at de.hybris.platform.lucenesearch.jalo.LuceneIndex.removeItemFromIndex( at de.hybris.platform.lucenesearch.jalo.UpdateIndexJob.performCronJob( at de.hybris.platform.cronjob.jalo.Job.execute( at de.hybris.platform.cronjob.jalo.Job.performImpl( at de.hybris.platform.cronjob.jalo.Job.access$1( at de.hybris.platform.cronjob.jalo.Job$ at

Searching on this portale we've found only this thread:

but was not helpful in the issue analysis.

Thanks in advance for the support.

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Feb 14, 2018 at 10:26 AM

    Hi Marcello,

    Yes - these jobs can be deactivated, either by impex (removing the jobs) or manually be deleting. Their purpose is to index search data within the HMC.

    If there has been a lot of data updates - ie data imported, naturally occuring due to a new project and these jobs have not been ran regularly, then they can take a long time to complete and affect performance of other running jobs, for example the front end solr index or other running cronjobs for that matter.

    I can't precisely pinpoint what is causing your specific exception, without more information but given that this should be disabled/removed, this will also negate the exception investigation.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.