Re: Replication issue with version 0 index in SOLR 7.5

One other question related to this. I know the change was made for a specific problem that was occurring but has this caused a similar problem as mine with anyone else? We're looking to try changing the second 'if' statement to add an extra conditional to prevent it from performing the "deleteAll

Re: Replication issue with version 0 index in SOLR 7.5

I removed the replicate after startup from our solrconfig.xml file. However that didn't solve the issue. When I rebuilt the primary, the associated replicas all went to 0 documents. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Replication issue with version 0 index in SOLR 7.5

Ok. probable dropping startup will help. Another idea set replication.enable.master=false and enable it when master index is build after restart. On Tue, Jun 25, 2019 at 6:18 PM Patrick Bordelon < patrick.borde...@coxautoinc.com> wrote: > We are currently using the replicate after commit and sta

Re: Replication issue with version 0 index in SOLR 7.5

We are currently using the replicate after commit and startup ${replication.enable.master:false} commit startup schema.xml,stopwords.txt -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Replication issue with version 0 index in SOLR 7.5

Note, it seems like the current Solr's logic relies on persistent master disks. https://github.com/apache/lucene-solr/blob/master/solr/core/src/test/org/apache/solr/handler/TestReplicationHandler.java#L615 On Tue, Jun 25, 2019 at 3:16 PM Mikhail Khludnev wrote: > Hello, Patrick. > Can commit he

Re: Replication issue with version 0 index in SOLR 7.5

Hello, Patrick. Can commit help you? On Tue, Jun 25, 2019 at 12:55 AM Patrick Bordelon < patrick.borde...@coxautoinc.com> wrote: > Hi, > > We recently upgraded to SOLR 7.5 in AWS, we had previously been running > SOLR > 6.5. In our current configuration we have our applications broken into a > si

Replication issue with version 0 index in SOLR 7.5

Hi, We recently upgraded to SOLR 7.5 in AWS, we had previously been running SOLR 6.5. In our current configuration we have our applications broken into a single instance primary environment and a multi-instance replica environment separated behind a load balancer for each environment. Until rece

Re: Master Slave Replication Issue

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

Re: Master Slave Replication Issue

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

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

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 swi

Re: Master Slave Replication Issue

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.l

Solr 7.2.1 Master-slave replication Issue

Hi, Facing issue in Solr 7.2.1 Master-slave replication, Master-slave replication is working fine. But if I disable replication from master, Slaves shows no data (numFound=0). Slave in not serving data, it had before replication. I suspect, Index generation is getting updated in slave, which was

Re: Master Slave Replication Issue

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

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 U

Master Slave Replication Issue

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

Re: SolrCloud Replication Issue

Amit: The fact that "all instances are using no more than 30%" isn't really indicative of whether or not GC pauses are a problem. If you have a large heap allocated to Java, then the to-be-collected objects will build up and _eventually_ you'll have a stop-the-world GC pause even though each t

Re: SolrCloud Replication Issue

Appreciate the response, to answer your questions. * Do you see this happen often? How often? It has happened twice in five days. The first two days after deployment. * Are there any known network issues? There are no obvious network issues but as these instances reside in AWS i cannot rule it ou

Re: SolrCloud Replication Issue

Looks like LeaderInitiatedRecovery or LIR. When a leader receives a document (update) but fails to successfully forward it to a replica, it marks that replica as down and asks the replica to recover (hence the name, Leader Initiated Recovery). It could be due to multiple reasons e.g. network issue/

SolrCloud Replication Issue

Hi, A few days ago I deployed a solr 4.9.0 cluster, which consists of 2 collections. Each collection has 1 shard with 3 replicates on 3 different machines. On the first day I noticed this error appear on the leader. Full Log - http://pastebin.com/wcPMZb0s 4/23/2015, 2:34:37 PM SEVERE SolrCmdDist

Re: SolR replication issue

The entire stacktrace: ERROR SolrIndexWriter Coud not unlock directory after seemingly failed IndexWriter#close() org.apache.lucene.store.LockReleaseFailedException: Cannot forcefully unlock a NativeFSLock which is held by another indexer component: /home/miapp/collection1/data/index.2014090114080

Re: SolR replication issue

On 9/1/2014 10:31 AM, Mauricio Ferreyra wrote: > I'm using Solr 4.3.1 with a master/slave configuration. > > Configuration: > > Master: > * * > * commit* > * startup* > * schema.xml,stopwords.txt* > * * > > > Slave: > * * > * http://10.xx.xx.xx:90

SolR replication issue

Hi folks, I'm using Solr 4.3.1 with a master/slave configuration. Configuration: Master: * * * commit* * startup* * schema.xml,stopwords.txt* * * Slave: * * * http://10.xx.xx.xx:9081/solr * * 00:00:60* *

Re: Replication Issue with Repeater Please help

On 8/16/2014 8:11 AM, waqas sarwar wrote: >> Thank you so much. You helped alot. One more question is that can i use only >> one zookeeper server to manage 3 solr servers, or i've to configure 3 >> zookeeper servers for each. >And zookeeper servers should be stand alone or >> better to use same

Re: Replication Issue with Repeater Please help

@elyograg.org >> To: solr-user@lucene.apache.org >> Subject: Re: Replication Issue with Repeater Please help >> >> On 8/14/2014 2:09 AM, waqas sarwar wrote: >> > Thanks Shawn. What i got is Circular replication is totally impossible & >> > Solr fails

RE: Replication Issue with Repeater Please help

> Date: Thu, 14 Aug 2014 06:51:02 -0600 > From: s...@elyograg.org > To: solr-user@lucene.apache.org > Subject: Re: Replication Issue with Repeater Please help > > On 8/14/2014 2:09 AM, waqas sarwar wrote: > > Thanks Shawn. What i got is Circular replication is totall

Re: Replication Issue with Repeater Please help

On 8/14/2014 2:09 AM, waqas sarwar wrote: > Thanks Shawn. What i got is Circular replication is totally impossible & Solr > fails in distributed environment. Then why solr documentation says that > configure "REPEATER" for distributed architecture, because "REPEATER" behave > like master-slave a

RE: Replication Issue with Repeater Please help

> Date: Wed, 13 Aug 2014 07:19:58 -0600 > From: s...@elyograg.org > To: solr-user@lucene.apache.org > Subject: Re: Replication Issue with Repeater Please help > > On 8/13/2014 12:49 AM, waqas sarwar wrote: > > Hi, I'm using Solr. I need a little bit assistanc

Re: Replication Issue with Repeater Please help

gt; suppose start with least no of nodes (suppose 3), how can i replicate data of > each node to 2 others and vice versa.My Solution:- I set up “REPEATER” on > all nodes, each node is master to other, and configured circular replication. > Issue i'm facing:- All nodes are wor

Replication Issue with Repeater Please help

can i replicate data of each node to 2 others and vice versa.My Solution:- I set up “REPEATER” on all nodes, each node is master to other, and configured circular replication. Issue i'm facing:- All nodes are working fine replicating data from other node, but when node1 replicate data

Re: Solr Replication Issue : Incorrect Base_URL

quot;:{ >"state":"down", > * "base_url":"http://hostname:8080/solr",* >"core":"reviews", >"node_name":"10.98.63.98:8080_solr"}, > > Can some

Solr Replication Issue : Incorrect Base_URL

per or solr cloud that the base url should be hostname:8080/raptorslrweb/solr and not hostname:8080/solr. Thanks, Pramod -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Replication-Issue-Incorrect-Base-URL-tp4141537.html Sent from the Solr - User mailing list archive at Nabble.com.

RE: Solr 4.4 - Master/Slave configuration - Replication Issue with Commits after deleting documents using Delete by ID

Thanks Shalin. Regards, Bharat Akkinepalli -Original Message- From: Shalin Shekhar Mangar [mailto:shalinman...@gmail.com] Sent: Thursday, October 17, 2013 1:18 AM To: solr-user@lucene.apache.org Subject: Re: Solr 4.4 - Master/Slave configuration - Replication Issue with Commits after

Re: Solr 4.4 - Master/Slave configuration - Replication Issue with Commits after deleting documents using Delete by ID

Bharat Akkinepalli. > > -Original Message- > From: Shalin Shekhar Mangar [mailto:shalinman...@gmail.com] > Sent: Wednesday, October 16, 2013 11:28 AM > To: solr-user@lucene.apache.org > Subject: Re: Solr 4.4 - Master/Slave configuration - Replication Issue > with Commit

RE: Solr 4.4 - Master/Slave configuration - Replication Issue with Commits after deleting documents using Delete by ID

rat Akkinepalli. -Original Message- From: Shalin Shekhar Mangar [mailto:shalinman...@gmail.com] Sent: Wednesday, October 16, 2013 11:28 AM To: solr-user@lucene.apache.org Subject: Re: Solr 4.4 - Master/Slave configuration - Replication Issue with Commits after deleting documents using Delete

Re: Solr 4.4 - Master/Slave configuration - Replication Issue with Commits after deleting documents using Delete by ID

October 11, 2013 2:16 PM > To: solr-user@lucene.apache.org > Subject: RE: Solr 4.4 - Master/Slave configuration - Replication Issue > with Commits after deleting documents using Delete by ID > > Hi Otis, > Thanks for the response. The log files can be found here. > >

RE: Solr 4.4 - Master/Slave configuration - Replication Issue with Commits after deleting documents using Delete by ID

@lucene.apache.org Subject: RE: Solr 4.4 - Master/Slave configuration - Replication Issue with Commits after deleting documents using Delete by ID Hi Otis, Thanks for the response. The log files can be found here. MasterLog : http://pastebin.com/DPLKMPcF Slave Log: http://pastebin.com

RE: Solr 4.4 - Master/Slave configuration - Replication Issue with Commits after deleting documents using Delete by ID

4.4 - Master/Slave configuration - Replication Issue with Commits after deleting documents using Delete by ID Bharat, Can you look at the logs on the Master when you issue the delete and the subsequent commits and share that? Otis -- Solr & ElasticSearch Support -- http://sematext.com/ Per

Re: Solr 4.4 - Master/Slave configuration - Replication Issue with Commits after deleting documents using Delete by ID

Bharat, Can you look at the logs on the Master when you issue the delete and the subsequent commits and share that? Otis -- Solr & ElasticSearch Support -- http://sematext.com/ Performance Monitoring -- http://sematext.com/spm On Tue, Oct 8, 2013 at 3:57 PM, Akkinepalli, Bharat (ELS-CON) wrot

Solr 4.4 - Master/Slave configuration - Replication Issue with Commits after deleting documents using Delete by ID

Hi, We have recently migrated from Solr 3.6 to Solr 4.4. We are using the Master/Slave configuration in Solr 4.4 (not Solr Cloud). We have noticed the following behavior/defect. Configuration: === 1. The Hard Commit and Soft Commit are disabled in the configuration (we control

Re: Solr External Scripts Replication Issue

Found the solution. It was related to solrdeletionpolicy. Phew!!! -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-External-Scripts-Replication-Issue-tp4093343p4093356.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Solr External Scripts Replication Issue

) at org.apache.solr.search.SolrIndexSearcher.getReader(SolrIndexSearcher.java:169) ... 34 more -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-External-Scripts-Replication-Issue-tp4093343p4093345.html Sent from the Solr - User mailing list archive at

Solr External Scripts Replication Issue

ll be appreciated. Thanks in advance -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-External-Scripts-Replication-Issue-tp4093343.html Sent from the Solr - User mailing list archive at Nabble.com.

replication issue on slaves

Hi We're using good old master-slave replication (not SolrCloud yet) Since we've upgraded to solr 4.3, replication causes the slave JVM to hiccup (probably heap & GC issues) *during the download phase*, which seemed strange to me because download was only supposed to copy files from the master to

Re: Replication Issue wit Solr 4.0.0

Well it seems to have resolved itself. Fully wiped the configuration directores and recreate the cores and it seems to be fixed. On Fri, Jan 25, 2013 at 1:11 PM, Sean Siefert wrote: > Unfortunately no such luck. If anyone thinks of anything to try I would > appreciate it. > > > On Fri, Jan 25,

Re: Replication Issue wit Solr 4.0.0

Unfortunately no such luck. If anyone thinks of anything to try I would appreciate it. On Fri, Jan 25, 2013 at 12:40 PM, Sean Siefert wrote: > Thanks for the response. That was my last resort attempt. I saw some > replication related fixes. I will reply if it works. > > > On Fri, Jan 25, 2013 a

Re: Replication Issue wit Solr 4.0.0

Thanks for the response. That was my last resort attempt. I saw some replication related fixes. I will reply if it works. On Fri, Jan 25, 2013 at 12:10 PM, Mark Miller wrote: > I don't have any targeted advice at the moment, but just for kicks, you > might try using Solr 4.1. > > - Mark > > On

Re: Replication Issue wit Solr 4.0.0

I don't have any targeted advice at the moment, but just for kicks, you might try using Solr 4.1. - Mark On Jan 25, 2013, at 2:47 PM, Sean Siefert wrote: > So I have quite a few cores already where this exact (as far as replication > is concerned) solrconfig.xml works. The other cores all repl

Replication Issue wit Solr 4.0.0

So I have quite a few cores already where this exact (as far as replication is concerned) solrconfig.xml works. The other cores all replicate correctly including conf files. And every core imports perfectly fine. The issue I am having is that the master doesn't seem to acknowledge anything except r

Re: 4.0 Strange Commit/Replication Issue

That is the problem. I wasn't aware of that new feature in 4.0. Thanks for the quick response Tomás. -Briggs On Wed, Aug 1, 2012 at 3:08 PM, Tomás Fernández Löbbe wrote: > Could your autocommit in the master be using "openSearcher=false"? If you > go to the Master admin, do you see that the sea

Re: 4.0 Strange Commit/Replication Issue

Could your autocommit in the master be using "openSearcher=false"? If you go to the Master admin, do you see that the searcher has all the segments that you see in the filesystem? On Wed, Aug 1, 2012 at 4:24 PM, Briggs Thompson wrote: > Hello all, > > I am running 4.0 alpha and have encountere

4.0 Strange Commit/Replication Issue

Hello all, I am running 4.0 alpha and have encountered something I am unable to explain. I am indexing content to a master server, and the data is replicating to a slave. The odd part is that when searching through the UI, no documents show up on master with a standard *:* query. All cache types a

Re: Replication Issue

Ugh, after a mess of additional flailing around, it appears I just discovered that the Replicate Now form on the Replication Admin page does not work in the text-based browser 'links'. :( Running /replication?command=fetchindex" with curl did the trick. Now everything is synced up. Thanks for you

Re: Replication Issue

Clocks on the separate machines are irrelevant, so don't worry about that bit. The index version _starts out_ as a timestamp as I understand it, but from there on when you change the index and commit it should just bump up NOT get a new timestamp. 1> it's strange that the version on the master wh

Re: Replication Issue

Nevermind, I realized that my master index was not tickling the index version number when a commit or optimize happened. I gave in and nuke and paved it, and now it seems fine. Is there any known reason why this would happen, so I can avoid this in the future? Thanks, Michael Della Bitta -

Replication Issue

Hi, I'm having trouble with replication on a brand new rollout of 3.6. Basically I've traced it to the slave always thinking the index it creates when it warms up is newer than what's on the master, no matter what I do... deleting the slave's index, committing or optimizing on the master, etc. I c

Re: replication issue

Hi I just want to post a follow up on the replication issue I encountered I have a master on which many document updates (delete and add) are happening There is one slave replicating from the master. There is only search request hitting the slave. I can see the size of the downloaded data

Re: replication issue

.. What could have possibly happen? --- On Tue, 3/2/10, Otis Gospodnetic wrote: From: Otis Gospodnetic Subject: Re: replication issue To: solr-user@lucene.apache.org Date: Tuesday, March 2, 2010, 4:40 PM Hi Matthieu, Does this happen over and over? Is this with Solr 1.4 or some other version?

Re: replication issue

search :: http://search-hadoop.com/ - Original Message > From: Matthieu Labour > To: solr-user@lucene.apache.org > Sent: Tue, March 2, 2010 4:35:46 PM > Subject: Re: replication issue > > The replication does not work for me > > > I have a big master solr and

Re: replication issue

wrote: From: Matthieu Labour Subject: Re: replication issue To: solr-user@lucene.apache.org Date: Tuesday, March 2, 2010, 3:35 PM The replication does not work for me I have a big master solr and I want to start replicating it. I can see that the slave is downloading data from the master

Re: replication issue

The replication does not work for me I have a big master solr and I want to start replicating it. I can see that the slave is downloading data from the master... I see a directory index.20100302093000 gets created in data/ next to index... I can see its size growing but then the directory gets

Re: replication issue

java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)     at java.lang.Thread.run(Thread.java:595) --- On Tue, 3/2/10, Matthieu Labour wrote: From: Matthieu Labour Subject: Re: replication issue To: solr

Re: replication issue

matt --- On Mon, 3/1/10, Noble Paul നോബിള്‍ नोब्ळ् wrote: From: Noble Paul നോബിള്‍ नोब्ळ् Subject: Re: replication issue To: solr-user@lucene.apache.org Date: Monday, March 1, 2010, 10:30 PM The data/index.20100226063400 dir is a temporary dir and isc reated in the same dir where the index d

Re: replication issue

The data/index.20100226063400 dir is a temporary dir and isc reated in the same dir where the index dir is located. I'm wondering if the symlink is causing the problem. Why don't you set the data dir as /raid/data instead of /solr/data On Sat, Feb 27, 2010 at 12:13 AM, Matthieu Labour wrote: > H

Re: replication issue

: replication issue To: solr-user@lucene.apache.org Date: Friday, February 26, 2010, 2:06 PM On Sat, Feb 27, 2010 at 12:13 AM, Matthieu Labour wrote: > Hi > > I am still having issues with the replication and wonder if things are > working properly > > So I have 1 master and

Re: replication issue

matt --- On Fri, 2/26/10, Shalin Shekhar Mangar wrote: From: Shalin Shekhar Mangar Subject: Re: replication issue To: solr-user@lucene.apache.org Date: Friday, February 26, 2010, 2:06 PM On Sat, Feb 27, 2010 at 12:13 AM, Matthieu Labour wrote: > Hi > > I am still having issues

Re: replication issue

On Sat, Feb 27, 2010 at 12:13 AM, Matthieu Labour wrote: > Hi > > I am still having issues with the replication and wonder if things are > working properly > > So I have 1 master and 1 slave > > On the slave, I deleted the data/index directory and > data/replication.properties file and restarted

replication issue

Hi I am still having issues with the replication and wonder if things are working properly So I have 1 master and 1 slave On the slave, I deleted the data/index directory and data/replication.properties file and restarted solr. When slave is pulling data from master, I can see that the size o

Re: master/slave replication issue

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 G wrote: > > > > > > > > Hello, > > I'm having an issue getting the master to replicate it

master/slave replication issue

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 t