Re: Master Slave Replication Issue

[Erick Erickson]

Hmmm, afraid I'm out of my depth, perhaps some of the Lucene
folks can chime in.

 Sorry I can't be more  help.
Erick
On Mon, Nov 12, 2018 at 12:27 AM damian.pawski  wrote:
>
> Hi
>
> I had to re-create the index as some tokenizers are not longer supported on
> the 7.x version.
> I have a fresh 7.x index.
>
> Thank you
> Damian
>
>
>
> --
> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Master Slave Replication Issue

[damian.pawski]

Hi

I had to re-create the index as some tokenizers are not longer supported on
the 7.x version.
I have a fresh 7.x index.

Thank you
Damian



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Master Slave Replication Issue

[damian.pawski]

Hi

I had to re-create the index, as some Tokenizers are no longer supported on
7.X, so I have a fresh 7.x index, but still having issues with the
replication.

Thank you
Damian



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Master Slave Replication Issue

[Erick Erickson]

Damian:

You say you've switched from 5x to 7x. Did you try to use an index
created with 5x or did you index fresh with 7x? Solr/Lucene do not
guarantee backward compatibility across more than one major version.

Best,
Erick
On Fri, Nov 9, 2018 at 2:34 AM damian.pawski  wrote:
>
> Hi,
> We have switched from 5.4 to 7.2.1 and we have started to see more issues
> with the replication.
> I think it may be related to the fact that a delta import was started during
> a full import (not the case for the Solr 5.4).
>
> I am getting below error:
>
> XXX: java.lang.IllegalArgumentException:java.lang.IllegalArgumentException:
> Directory MMapDirectory@XXX\index
> lockFactory=org.apache.lucene.store.NativeFSLockFactory@21ff4974 still has
> pending deleted files; cannot initialize IndexWriter
>
> Are there more known issues with Solr 7.X and the replication?
> Based on https://issues.apache.org/jira/browse/SOLR-11938 I can not trust
> Solr 7.X anymore.
>
> How can I fix the
> "XXX: java.lang.IllegalArgumentException:java.lang.IllegalArgumentException:
> Directory MMapDirectory@XXX\index
> lockFactory=org.apache.lucene.store.NativeFSLockFactory@21ff4974 still has
> pending deleted files; cannot initialize IndexWriter
> "
> issue?
>
> Thank you
> Damian
>
>
>
> --
> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Master Slave Replication Issue

[damian.pawski]

Hi, 
We have switched from 5.4 to 7.2.1 and we have started to see more issues
with the replication.
I think it may be related to the fact that a delta import was started during
a full import (not the case for the Solr 5.4).

I am getting below error:

XXX: java.lang.IllegalArgumentException:java.lang.IllegalArgumentException:
Directory MMapDirectory@XXX\index
lockFactory=org.apache.lucene.store.NativeFSLockFactory@21ff4974 still has
pending deleted files; cannot initialize IndexWriter

Are there more known issues with Solr 7.X and the replication?
Based on https://issues.apache.org/jira/browse/SOLR-11938 I can not trust
Solr 7.X anymore.

How can I fix the 
"XXX: java.lang.IllegalArgumentException:java.lang.IllegalArgumentException:
Directory MMapDirectory@XXX\index
lockFactory=org.apache.lucene.store.NativeFSLockFactory@21ff4974 still has
pending deleted files; cannot initialize IndexWriter
"
issue?

Thank you
Damian



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Master Slave Replication Issue

[den_nal]

Done https://issues.apache.org/jira/browse/SOLR-11938.

Thanks!



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Master Slave Replication Issue

[Tomas Fernandez Lobbe]

This seems pretty serious. Please create a Jira issue

Sent from my iPhone

> On Feb 1, 2018, at 12:15 AM, dennis nalog  
> wrote:
> 
> Hi,
> We are using Solr 7.1 and are solr setup is master-slave replication.
> We encounter this issue that when we disable the replication in master via UI 
> or URL (server/solr/solr_core/replication?command=disablereplication), the 
> data in our slave servers suddenly becomes 0.
> Just wanna know if this is a known issue or this is the expected behavior. 
> Thanks in advance.
> Best regards,Dennis

Re: master/slave replication issue

[Noble Paul നോബിള്‍ नोब्ळ्]

The log messages are shown when you hit the admin page. So on't worry
about that. Keep a minimal configuration of Replication. All you need
is  masterUrl and pollInterval.


On Thu, Aug 27, 2009 at 5:52 AM, J Gskinny_joe...@hotmail.com wrote:







 Hello,

 I'm having an issue getting the master to replicate its index to the slave. 
 Below you will find my configuration settings. Here is what is happening: I 
 can access the replication dashboard for both the slave and master and I can 
 successfully execute HTTP commands against both of these urls through my 
 browser. Now, my slave is configured to use the same URL as the one I am 
 using in my browser when I query the master, yet when I do a tail -f tomcat 
 home/logs/catalina.out on the slave server all I see is :


 Master - server1.xyz.com Aug 27, 2009 12:13:29 AM 
 org.apache.solr.core.SolrCore execute

 INFO: [] webapp=null path=null params={command=details} status=0 QTime=8

 Aug 27, 2009 12:13:32 AM org.apache.solr.core.SolrCore execute

 INFO: [] webapp=null path=null params={command=details} status=0 QTime=8

 Aug 27, 2009 12:13:34 AM org.apache.solr.core.SolrCore execute

 INFO: [] webapp=null path=null params={command=details} status=0 QTime=4

 Aug 27, 2009 12:13:36 AM org.apache.solr.core.SolrCore execute

 INFO: [] webapp=null path=null params={command=details} status=0 QTime=4

 Aug 27, 2009 12:13:39 AM org.apache.solr.core.SolrCore execute

 INFO: [] webapp=null path=null params={command=details} status=0 QTime=4

 Aug 27, 2009 12:13:42 AM org.apache.solr.core.SolrCore execute

 INFO: [] webapp=null path=null params={command=details} status=0 QTime=8

 Aug 27, 2009 12:13:44 AM org.apache.solr.core.SolrCore execute

 INFO: [] webapp=null path=null params={command=details} status=0 QTime=


 For some reason, the webapp and the path is being set to null and I think 
 this is affecting the replication?!? I am running Solr as the WAR file and 
 it's 1.4 from a few weeks ago.



 requestHandler name=/replication class=solr.ReplicationHandler 
    lst name=master
        !--Replicate on 'optimize'. Other values can be 'commit', 'startup'. 
 It is possible to have multiple entries of this config string--
        str name=replicateAfteroptimize/str

        !--Create a backup after 'optimize'. Other values can be 'commit', 
 'startup'. It is possible to have multiple entries of this config string 
 .note that this is just for backup. Replication does not require this --
        str name=backupAfteroptimize/str

        !--If configuration files need to be replicated give the names here, 
 separated by comma --
        !--str name=confFilesschema.xml,stopwords.txt,elevate.xml/str--
    /lst
 /requestHandler
 Notice that I commented out the replication of the configuration files. I 
 didn't think this is important for the attempt to try to get replication 
 working. However, is it good to have these files replicated?


 Slave - server2.xyz.com

 requestHandler name=/replication class=solr.ReplicationHandler 
    lst name=slave

        !--fully qualified url for the replication handler of master . It is 
 possible to pass on this as a request param for the fetchindex command--
        str 
 name=masterUrlhttp://server1.xyz.com:8080/jdoe/replication/str

        !--Interval in which the slave should poll master .Format is HH:mm:ss 
 . If this is absent slave does not poll automatically.
         But a fetchindex can be triggered from the admin or the http API --
        str name=pollInterval00:00:20/str
        !-- THE FOLLOWING PARAMETERS ARE USUALLY NOT REQUIRED--
        !--to use compression while transferring the index files. The 
 possible values are internal|external
         if the value is 'external' make sure that your master Solr has the 
 settings to honour the accept-encoding header.
         see here for details http://wiki.apache.org/solr/SolrHttpCompression
         If it is 'internal' everything will be taken care of automatically.
         USE THIS ONLY IF YOUR BANDWIDTH IS LOW . THIS CAN ACTUALLY SLOWDOWN 
 REPLICATION IN A LAN--
        str name=compressioninternal/str
        !--The following values are used when the slave connects to the 
 master to download the index files.
         Default values implicitly set as 5000ms and 1ms respectively. The 
 user DOES NOT need to specify
         these unless the bandwidth is extremely low or if there is an 
 extremely high latency--
        str name=httpConnTimeout5000/str
        str name=httpReadTimeout1/str

        !-- If HTTP Basic authentication is enabled on the master, then the 
 slave can be configured with the following --
        str name=httpBasicAuthUserusername/str
        str name=httpBasicAuthPasswordpassword/str

     /lst
 /requestHandler



 Thanks for your help!




 _
 Hotmail® is up to 70% faster. Now good news travels really fast.