Details

    • Bug Priority:
      Category 2
    • ACT Numbers:

      137453 Premier

      Description

      Many customers are asking for support of the built in solr replication mechanism available since solr 1.4
      see
      http://wiki.apache.org/solr/SolrReplication
      (this is not the rsync command line sync feature)

      This ticket is aimed at tracking the list of customers asking for it.

      Notes:
      1) http://wiki.alfresco.com/wiki/Alfresco_And_SOLR
      mentions "there is currently no slave replication support"
      2) if you have three solr nodes, having each of them tracking put an unnecessary load on the the SQL database. Solr replication makes more sense
      3) many customers have been trying to do it.
      It seems that with 4.14, we are not far from having it work.
      see ticket 137453

      The index replication works nicely but we are faced with an issue of index cleanup on the slave

      2013-10-18 10:59:30,081 WARN [alfresco.solr.AlfrescoSolrEventListener] [pool-5-thread-1] Cache state error -> rebuilding
      java.lang.IllegalStateException: New sub reader but no new docs ??
      at org.alfresco.solr.AlfrescoSolrEventListener.buildCacheUpdateOperations(AlfrescoSolrEventListener.java:1063)
      at org.alfresco.solr.AlfrescoSolrEventListener.newSearcher(AlfrescoSolrEventListener.java:325)
      at org.apache.solr.core.SolrCore$4.call(SolrCore.java:1163)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:662)
      2013-10-18 10:59:59,674 WARN [solr.handler.SnapPuller] [pool-8-thread-1] The update handler is not an instance or sub-class of DirectUpdateHandler2. ReplicationHandler may not be able to cleanup unused index files.

      We have tested adding, modifying and deleting and the Slave Solr is staying in sync with the Master Solr. The only thing is, the Slave Solr cannot cleanup after itself so the Slave is growing over time in disk usage.

      What the plans with Alfresco to fully implement Solr replication as for the most part it works really well.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedissues Closed Issues
                  Reporter:
                  amadon Alex Madon [X] (Inactive)
                • Votes:
                  12 Vote for this issue
                  Watchers:
                  24 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel