Alfresco lucene Index

[itayh]

Hi,

I have several questions about lucene in alfresco.
I could not find documentations on those issues.

1 - What is archive folder under \lucene-indexes means?
2 - Can I set <index enabled="false"> for specific items and then they will not be index
3 - What <archive>true</archive> in cm:content mean?
4 - basically I want to reduce the size and number of files/folders under lucene-indexes.

Any Ideas?

Thanks a lot in advance,
Itay

[andy]

Hi

The back up does a file copy while holding an index lock. Check how fast files can be copied around the disks.

What version of Alfresco are you using?

Can you post the directory listings for …
/opt/alfresco/*/*/indexes/workspace
and each sub directory


Andy

[itayh]

Hi,

We are using Alfresco 2.1 community version.

Link to directories list can be found here: http://212.72.51.81/ilya/alfresco.list.txt

Copy time on our server:
(1) node-7, 785M, 1454 files
# time rsync -a node-7 node-7.test
real 2m58.333s
user 0m6.356s
sys 0m10.817s

Thx
  Itay

[andy]

Hi

Your index structure has rubbish in it.
You could rebuild this.

This is often caused by failing to close a results set (from the Java API)
Have you written any of your own code or is this a standard Alfresco install?

Andy

[itayh]

Thank you for the answer.

Yes we add some code and the close was not in finally.

Maybe that was the problem.

One more issue. We notice that if we perform action on space (our own action written in java API) and got exception sometimes the space just disappear from the screen.
In this case we need to build the whole index's again (FULL in the index rebuild in repository.properties).

Do you have any idea on that?

Thank you in advance,
Itay

[ebell]

Does someone have any information about what exactly is occurring that takes over an hour?  We're looking to use Alfresco with around the clock direct uploads.  Is there a way to restrict the backup indexing?

[robertito]

Good Day,

we are using Alfresco 3.0 Labs and we also extended it by using its API. We have the same problem about the index that grows. 
Could you explain a little bit more of what you exactly mean about closing the result sets or provide some examples?
Also, you explained that Alfresco takes a lock on the indexes and copies them to the backup directory.  But the process takes way too long compared to manual copying the indexes. Is there anything else going on within this process? Maybe shrinking the indexes (we know this takes a long time). Is there no work around for this except turning off the index backup job altogether?

Thank you very much!

[msporled]

Does someone have any information about what exactly is occurring that takes over an hour?  We're looking to use Alfresco with around the clock direct uploads.  Is there a way to restrict the backup indexing?

Check out scheduled-jobs-context.xml

    <bean id="indexBackupTrigger" class="org.alfresco.util.CronTriggerBean">
        <property name="jobDetail">
            <ref bean="indexBackupJobDetail" />
        </property>
        <property name="scheduler">
            <ref bean="schedulerFactory" />
        </property>
        <!– trigger at 3am each day –>
        <property name="cronExpression">
            <value>0 0 3 * * ?</value>
        </property>
    </bean>
‍‍‍‍‍‍‍‍‍‍‍‍‍

[andy]

Hi

The issue was caused by custom code not closing query results sets, so old index data was left behind leading to a very large backup.
This will happen if result sets are left unclosed.


Andy

[tejaskanani2920]

Hi ,

I want to do Full Indexing in alfresco. i am using Alfresco 2.1.1
But if i do it by just using adding index.recovery.mode=FULL in repository.properties it will do Full Indexing when i restart the alfresco but it took lot of time as i am having lots of spaces in my alfresco repository and by that time i am not able to use alfresco at all till it finish the Full Indexing.
so for that i create one class which takes transaction range as a parameter (0-16000)and it does reindex for that given range of transactions. And i can run that process without disturbing the alfresco as it reads the transactions from databases directly.
so by that way i just divide the Full Indexing in 2 parts.

for example,
if my alf_transaction table contains 32000 transactions.
then i just divide it to 0-16000 and 160001-32000.
Basically it creates two separate folder like lucene-indexes-0-16000 and lucene-indexes-16001-32000.
so lucene-indexes-0-16000 contains index backup of 0 to 16000 transactions. And lucene-indexes-16001-32000 contains index backup of 16001-32000 transactions.

so my final Full Indexing i want to merge those 2 index folders.
but now m getting the problem that how to merge those two different index folders ?
Is there any way in alfresco that will merge those two indexes folder ??

or if anybody gone through this type of stuff before please guide me …

Thanks,

[ebell]

Does someone have any information about what exactly is occurring that takes over an hour?  We're looking to use Alfresco with around the clock direct uploads.  Is there a way to restrict the backup indexing?

See the section on Lucene Index Restoration on http://wiki.alfresco.com/wiki/Backup_and_Restore