topic Re: No lucene synchronization on alfresco community 2.1 in Alfresco Archive

No lucene synchronization on alfresco community 2.1

seb — Sat, 24 Jan 2009 12:36:11 GMT

Hello,I'am trying to install Alfresco 2.1 community in cluster on JBoss 4.2.2.I used the following manual http://wiki.alfresco.com/wiki/Cluster_C … Clustering, but the lucene synchronization doesn't working.The cache replication seems to works fine and I have tested successfully an update propagatio

Re: No lucene synchronization on alfresco community 2.1

derek — Wed, 25 Feb 2009 15:02:00 GMT

Hi,
Your config looks fine, but you should upgrade to the Labs3 latest. There have been numerous fixes to critical bugs in the index tracking in the interim.
Regards

Re: No lucene synchronization on alfresco community 2.1

sreevals — Mon, 30 Jan 2012 12:31:16 GMT

I am using rxactly the same configurations mentioned in this thread. And is sure that the fix is going to be as suggested by Derek which is upgrade to the "Labs3". I searched around it and observed that "Labs3" is the new name for Alfresco Community Edition (http://wiki.alfresco.com/wiki/Alfresco_Labs_3). So does it mean that "Labs3" is a FREELY downloadable version. Since I am using 2.1.0, I have visited http://wiki.alfresco.com/wiki/General_Upgrade_Process#The_Upgrade_Process to understand the upgrade steps from 2.1.0 Community Edition to the so called "Labs3" (Alfresco_Labs_3). But the upgrade path was mentioned only for Alfresco Enterprise releases.

Precisely, Is there a way to upgrade to "labs3" from 2.1.0 Community Edition FREELY without going for Enterprise Edition and get the fix for the lucene issues mentioned here

Re: No lucene synchronization on alfresco community 2.1

mrogers — Mon, 30 Jan 2012 12:56:13 GMT

Yes you can freely upgrade to one of the later community versions. Although you will have to go though at least 1 intermediate version, the jump from 2.1 to 4.0 is too big.

Please note that Labs3 is now seriously out of date although you can still use it, just as you have been using 2.1

There were also fairly big changes to simplify the way that alfresco is configured for versions > 3.2.

Re: No lucene synchronization on alfresco community 2.1

sreevals — Mon, 30 Jan 2012 17:32:58 GMT

Thank you for the quick response.

My only concern is to make the lucene synchronisation work smoothly. For this which is simplest way? To which community version I need to upgrade. Also, could you please suggest where can I find the upgradation instructions to that version. Becoz the upgrade path that I have looked at (http://wiki.alfresco.com/wiki/General_Upgrade_Process#The_Upgrade_Process) clearly mention that those are for Alfresco Enterprise releases

Regards

Sreevals

Re: No lucene synchronization on alfresco community 2.1

derek — Mon, 30 Jan 2012 23:33:34 GMT

Yep.
You're going to have to try some upgrade paths out. My suggestion is that you take a stab at 2.1 to 3.4.d. If that works, go to 4.0 but 3.4.d will include many of the index fixes while 4.0 introduces SOLR, which takes it to a whole new level.
If you struggle on the 2.1 to 3.4.d upgrade, it's either something that can be sorted out or we'd have to go back to QA and find out which upgrades they tested for the community builds.
As an aside: you could, of course, get some support and access to the latest service packs and supported upgrade paths.

Re: No lucene synchronization on alfresco community 2.1

sreevals — Tue, 31 Jan 2012 03:19:33 GMT

Thank you.

The reason being I am so specific about Community Edition and Enterprise Edition is; it was mentioned in the release notes of 2.1 (http://wiki.alfresco.com/wiki/Release_2.1 - see "Important Notes") that the 2.1 Community Release distribution requires an additional library when activating clustering and a fix will be provided in time for the 2.1.0 Enterprise Release. And jira page for this bug (AR-1614) was not opening unfortunately. Otherwise I could have checked whether this fix is available in any of the subsequent community editions

Regards

Sreevals

Re: No lucene synchronization on alfresco community 2.1

derek — Tue, 31 Jan 2012 10:15:17 GMT

With a very few exceptions, we do not support 2.1 anymore. You need to upgrade.

Re: No lucene synchronization on alfresco community 2.1

sreevals — Mon, 06 Feb 2012 12:42:47 GMT

.

Thank you for your time.

The Release notes of 2.1 (http://wiki.alfresco.com/wiki/Release_2.1) suggests that "The appropriate version of the JSR 166 Backport must be dropped into your app server" as an additional library when activating clustering . So I am thinking to try this, to avoid an upgrade since upgrading involves lot of risks especially in terms of timeline. But can you suggest whether this can fix the lucene index issue.

btw, Any idea on what exactly is issue AR-1614 mentioned in the release notes. Because https://issues.alfresco.com/browse/AR-1614 land up no-where

Regards

Sreevals

Re: No lucene synchronization on alfresco community 2.1

derek — Mon, 06 Feb 2012 12:50:43 GMT

You need to upgrade. I can't see how dropping in untested backport of a library into a release is less risky than upgrading to a tested (and currently-supported) release.

Re: No lucene synchronization on alfresco community 2.1

mrogers — Mon, 06 Feb 2012 13:00:53 GMT

There are no longer any details of that old issue, it was obsolete and probably not migrated to the current JIRA database. Or was cleaned up.

Re: No lucene synchronization on alfresco community 2.1

derek — Mon, 06 Feb 2012 13:08:36 GMT

Exactly. V2.1 is no longer supported and issues of that age are archived internally for support.

Re: No lucene synchronization on alfresco community 2.1

sreevals — Tue, 07 Feb 2012 10:43:04 GMT

Okay.

So, Is there a suggested upgrade path from 2.1.0 community edition to any of the 3.x community edition in which the problem of lucene index is fixed and tested ? OR Fix for lucene index is not available in community edition at all ?

Regards

Sreevals

Re: No lucene synchronization on alfresco community 2.1

derek — Wed, 08 Feb 2012 10:46:58 GMT

From http://docs.alfresco.com/4.0/topic/com.alfresco.enterprise.doc/concepts/upgrade-path.html

Previous service pack. For Legacy upgrades, Alfresco recommend engaging consulting. 1.2 - 2.1 SP4

It's the timing and testing of the fixes that is not guaranteed for Community, but we do merge all fixes into the Community code. Our Enterprise releases start life on a Community code line and gradually build up fixes (tested and supported) that are eventually merged into the Community code.

Whatever fix you are after on a 2.1 release is in 3.4.d. And you should upgrade to 4.0.d and switch to SOLR and be done.

Re: No lucene synchronization on alfresco community 2.1

sreevals — Wed, 08 Feb 2012 11:45:05 GMT

.

Thank you very much for the guidance.

I Agreed; I have to upgrade from 2.1.0. I will go through the documentation link provided.

Regards

Sreevals

Re: No lucene synchronization on alfresco community 2.1

sreevals — Thu, 09 Feb 2012 14:43:10 GMT

Hi Again,

I have checked the upgrade link (http://docs.alfresco.com/4.0/topic/com.alfresco.enterprise.doc/concepts/upgrade-path.html)

Does the 2.1.0 community edition falls under the above quoted category (Legacy Upgrade) ? But the another line from the same link says community Ed (hope 2.1.0) can be upgraded to 3.0 SP1. Confusing . (eight line in the table on the above link- quoted below)

2.1 SP7; 2.2 SP3; 3.0 SP1; Community 3.1

Also seen from another posting by mrogers that community edition does not have service packs.

FROM 2.1.0 community edition, I would like to upgrade to 3.1 or 3.4.d (hope the lucene sync issue fix is available in this, as understood from the above postings). I have 2 questions .

1. Is there a suggested way to do this?
2. Whether this upgrade from 2.1.0 Community Edition is treated as a legacy upgrade ?

Regards

Sreevals

Re: No lucene synchronization on alfresco community 2.1

sreevals — Fri, 10 Feb 2012 11:08:24 GMT

Hi Again,

I have gone through the suggested upgrade path (http://docs.alfresco.com/4.0/topic/com.alfresco.enterprise.doc/concepts/upgrade-path.html). It looks like I have to have SPs to start upgrade. But in another thread from mrogers confirms that service packs are not available for Community Edition. Again the above link suggests that 'community' can be upgraded to 3.1. (9th line in the table at the above link - quoted below).

2.1 SP7; 2.2 SP3; 3.0 SP1; Community 3.1

So, its bit unclear and little confusing .

I want to upgrade from 2.1.0 Community Edition to the one of the 3.x Community version. Since this can fix the lucene index issue (As I understood from the above discussions). I have two questions.

1. Is there a suggested way to do this?
2. Does this upgrade is treated as a legacy upgrade as mentioned in the above post ?

Regards

Sreevals

Re: No lucene synchronization on alfresco community 2.1

mrogers — Fri, 10 Feb 2012 11:30:56 GMT

Please don't repeat your postings. You have been given the answers.

Either upgrade to Labs 3 Stable, or Community 3.4.d.