Filesystem snapshot backups & lucene index | Community
Skip to main content
S
sneakybeaky
Level 2
October 16, 2015
Solved

Filesystem snapshot backups & lucene index

  • October 16, 2015
  • 2 replies
  • 1696 views

Hi,

We're looking into using the filesystem snapshot backup method, which is extremely fast. The important part is suspending all writes to disk while the filesystem snapshot is taken. According to the docs invoking the JMX operation blockRepositoryWrites on the MBean com.adobe.granite:type=Repository prevents CRX writing to disk. My question is, does this also suspend lucene indexes being written as well (is lucene seen as part of CRX) ? 

If lucene operations aren't suspended there is a chance that the indexes get scrambled, which would mean deleting the indexes to recover which can mean a considerable recovery time.

Thanks,

Jon.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

Jon,

Technically writing to lucene is not suspended. But as the Lucene index updates are executed immediately after the save to the TarPM, they are part of the transaction. So the block of TarPM write activities will also block Lucene index updates.

And to every rule there is an exception: Large binaries are updated asynchronously; AFAIK they are not affected by this suspend.

Jörg

2 replies

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Jon,

Technically writing to lucene is not suspended. But as the Lucene index updates are executed immediately after the save to the TarPM, they are part of the transaction. So the block of TarPM write activities will also block Lucene index updates.

And to every rule there is an exception: Large binaries are updated asynchronously; AFAIK they are not affected by this suspend.

Jörg

S
sneakybeakyAuthor
Level 2
October 16, 2015

Thanks Jörg, that is extremely helpful.

Terms & ConditionsAccessibility statement

Loading footer...