Skip navigation
Currently Being Moderated

Lucene Index Disable

Mar 6, 2013 11:07 AM

Tags: #migration #dam #memory_crash #lucene

Hi We are trying bulk CQ DAm migration. It went on fine for 27k images after that memory exception came and number of files opened crossed beyond 60k on the server. We are guessing this is happening because of the lucene indexing is happening in the background is there any way to stop this during migration after that can we index? If yes please provide steps for stopping this Lucene index in 5.5 sp2.

 
Replies
  • Currently Being Moderated
    Mar 6, 2013 10:21 PM   in reply to maruthid

    I would guess the root cause for the problems are the workflows (indexing images should not put much load to lucene) - do you migrate directly in CQ DAM (already existing DAM assets)?

     

    If so, you can disable the DAM workflows during the migration.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 6, 2013 11:37 PM   in reply to maruthid

    Hi Maruthid

     

    if time is not the problem perhaps a wait time between importing the single images could help. I guess the problem is the generation of multiple renditions of the images (as image processing in java is expensive) - minimizing the count of generated renditions would also bring some performance optimizations for the migration.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points