Though unusual, it is possible for the Lucene indexer indexes used for text searches to get out of step (for example, after a system crash).
...
- Log in to the JMX-Console:
https://yoursite/jmx-console - Select "org.bedework" from the left-most "Object Name Filter" menu. "org.bedework" is usually the bottommost link.
- Select "service=Indexer"
- Click the button "Invoke" for the operation "rebuildIndex" (this is the bottommost operation in the list).
Note: this process may take a while.
...
When completed successfully, you should see a message such as the following in your JMX console (your numbers will be larger, depending on the size and age of your installation):
Code Block |
---|
[About to build directories at [yourPathHere]\jboss-5.1.0.GA\server\default\data\bedework\/lucene/indexroot/new , Statistics for User , users: 26 , collections: 128 , entities: 0 , unreachableEntities: 0 , Statistics for Public , users: 0 , collections: 71 , entities: 8 , unreachableEntities: 0 , About to rename directories from [yourPathHere]\jboss-5.1.0.GA\server\default\data\bedework\/lucene/indexroot/current to [yourPathHere]\jboss-5.1.0.GA\server\default\data\bedework\/lucene/indexroot/old , Unable to rename current index at [yourPathHere]\jboss-5.1.0.GA\server\default\data\bedework\/lucene/indexroot/current to [yourPathHere]\jboss-5.1.0.GA\server\default\data\bedework\/lucene/indexroot/old ] |