Basic Authentication in clusters is not supported as of today in CDCR.
On Fri, 7 Sep 2018, 4:53 pm Mrityunjaya Pathak,
wrote:
> I have setup two solr cloud instances in two different Datacenters Target
> solr cloud machine is copy of source machine with basicAuth enabled on
> them. I am unable
I have setup two solr cloud instances in two different Datacenters Target solr
cloud machine is copy of source machine with basicAuth enabled on them. I am
unable to see any replication on target.
Solr Version :6.6.3
I have done config changes as suggested on
I have setup two solr cloud instances in two different Datacenters Target solr
cloud machine is copy of source machine with basicAuth enabled on them. I am
unable to see any replication on target.
Solr Version :6.6.3
I have done config changes as suggested on
On 10/10/2017 2:51 AM, solr2020 wrote:
i could see different version of the below entries in Leader and replica.
While doing index , in replica instance logs we could see it is keep
receiving update request from leader but it says no changes, skipping
commit.
Master (Searching)
Master
The problem was replicationFactor was set to 1.Now replication works fine
while setting replicationFactor as 2.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
i could see different version of the below entries in Leader and replica.
While doing index , in replica instance logs we could see it is keep
receiving update request from leader but it says no changes, skipping
commit.
Master (Searching)
Master (Replicable)
There is no other error
thanks.
We dont see any error message/any message in logs. And we have enough disk
space.
We are running solr as root user in ubuntu box but zookeeper process running
as zookeeper user.Will that cause the problem?
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi,
We are using Solr 6.4.2 & SolrCloud setup. We have two solr instances in the
solr cluster.This solrcloud running in ubuntu OS. The problem is replication
is not happening between these two solr instances. sometimes it replicate
10% of the content and sometimes not.
In Zookeeper ensemble we
We need a lot more data to say anything useful, please read:
https://wiki.apache.org/solr/UsingMailingLists
What do you see in your Solr logs? What have you tried to do to
diagnose this? Do you have enough disk space?
Best,
Erick
On Thu, Oct 5, 2017 at 6:56 AM, solr2020
Hi,
We are using Solr 6.4.2 & SolrCloud setup. We have two solr instances in the
solr cluster.This solrcloud running in ubuntu OS. The problem is replication
is not happening between these two solr instances. sometimes it replicate
10% of the content and sometimes not.
In Zookeeper ensemble we
Is this some kind of typo in your slave configuration? 'cause it's
kinda weird. The error
mentioning collection1 indicates I think that the masterUrl is not
parseable (and somehow
doesn't throw a parsing error on startup) and the old default was "collection1".
This URL should point to a single
All,
I have solr 4.7 installed in a Windows 7 environment. My solrconfig.xml on the
master is:
${master.replication.enabled:true}
commit
startup
optimize
optimize
commit
:30 PM
To: solr-user@lucene.apache.org
Subject: RE: Replication not working
This is the log when the slave is polling.
But it's onlythe last two times.
As you can see, the time in between is ~ 2 minutes.
It it's from interest, I can post complete log from fresh restart on.
-Original Message
Hi all,
we have a setup with multiple cores, loaded via DataImportHandlers.
Works fine so far.
Now we are trying to get the replication working (for one core so far).
But the automated replication is never happening.
Manually triggered replication works!
Environment:
Solr 4.1 (also
with multiple cores, loaded via DataImportHandlers.
Works fine so far.
Now we are trying to get the replication working (for one core so far).
But the automated replication is never happening.
Manually triggered replication works!
Environment:
Solr 4.1 (also tried with 4.3)
App-Server JBoss 4.3
, 11. Juni 2013 13:16
An: solr-user@lucene.apache.org
Betreff: Re: Replication not working
can you check with the indexversion command on both mater and slave?
pollInterval is set to 2 minutes. It is usually long . So you may need to
wait for 2 mins for the replication to kick in
On Tue, Jun 11
/response
pollInterval is set to 2 minutes. It is usually long
I know ;-)
-Ursprüngliche Nachricht-
Von: Noble Paul നോബിള് नोब्ळ् [mailto:noble.p...@gmail.com]
Gesendet: Dienstag, 11. Juni 2013 13:16
An: solr-user@lucene.apache.org
Betreff: Re: Replication not working
can you
@lucene.apache.org
Betreff: Re: Replication not working
You said polling is happening and nothing is replicated
What do the logs say on slave (Set level to INFO) ?
On Tue, Jun 11, 2013 at 4:54 PM, thomas.poroc...@der.net wrote:
Calling indexversion on master gives:
response
lst name
}
-Ursprüngliche Nachricht-
Von: Noble Paul നോബിള് नोब्ळ् [mailto:noble.p...@gmail.com]
Gesendet: Dienstag, 11. Juni 2013 13:41
An: solr-user@lucene.apache.org
Betreff: Re: Replication not working
You said polling is happening and nothing is replicated
What do the logs say on slave
: Tuesday, June 11, 2013 2:24 PM
To: solr-user@lucene.apache.org
Subject: Re: Replication not working
I mean , the log when polling happens when from slave. Not when you issue a
command.
On Tue, Jun 11, 2013 at 5:28 PM, thomas.poroc...@der.net wrote:
Log on slave:
2013-06-11 13:19:08,477 8385607
Yeh the drop index via the URL command doesn't help anyway - when rebuilding
the index the timestamp is obviously ahead of master (as the slave is being
created now) so the replication will still not happen.
On 21 Dec 2011, at 16:37, Dean Pullen wrote:
I can't see a way, if the slave is on
We're simply restoring the master via a backed up snapshot (created using the
ReplicationHandler) and then trying to get the slave to replicate it.
On 21 Dec 2011, at 18:09, Erick Erickson wrote:
You can't. But index restoration should be a very rare thing,
or you have some lurking problem in
On 12/22/2011 4:39 AM, Dean Pullen wrote:
Yeh the drop index via the URL command doesn't help anyway - when rebuilding
the index the timestamp is obviously ahead of master (as the slave is being
created now) so the replication will still not happen.
If you deleted the index and create the
Hi all,
I have an odd problem locally when attempting replication with solr 1.4
The problem is, though the master files get copied to a temp directory in the
slave data directory (I see this happen at runtime), they are then not copied
over the actual slave index data.
We were wondering if it
E.g. I see this in the slave logs:
2011-12-21 15:45:27,635 INFO handler.SnapPuller:265 - Master's version:
1271406570655, generation: 376
2011-12-21 15:45:27,635 INFO handler.SnapPuller:266 - Slave's version:
1271406571565, generation: 1286
2011-12-21 15:45:27,636 INFO handler.SnapPuller:267
You've probably hit it on the head. The slave version is greater than the master
version, so replication isn't necessary. BTW, the version starts
life as a timestamp,
but then is simply incremented on successive commits, which accounts for
what you are seeing.
You should be able to blow the index
Thought as much, thanks for the reply.
Is there an easy way of dropping the index on the slave, or do I have to
manually delta the index files?
Regards,
Dean.
On 21 Dec 2011, at 15:54, Erick Erickson wrote:
You've probably hit it on the head. The slave version is greater than the
master
I can't see a way, if the slave is on another server.
We're going to upgrade solr - as you can delete the index after unloading a
core in this way:
cores?action=UNLOADcore=liveCoredeleteIndex=true
From v3.3 (I think)
On 21 Dec 2011, at 16:11, Dean Pullen wrote:
Thought as much, thanks for
Be careful deleting the index manually. Delete the entire index directory,
i.e. the data dir has no index directory under it.
About copying the index from the slave to the master, just shut down
the master, delete all the files from the index, and use scp or something
to copy the files in the
I can't understand, then, how we could ever restore and get replication to work
without manual intervention!
Dean
On 21 Dec 2011, at 16:37, Dean Pullen wrote:
I can't see a way, if the slave is on another server.
We're going to upgrade solr - as you can delete the index after unloading a
You can't. But index restoration should be a very rare thing,
or you have some lurking problem in your process.
Or this is an XY problem, what problem are you trying to
solve? see: http://people.apache.org/~hossman/#xyproblem
Best
Erick
On Wed, Dec 21, 2011 at 12:21 PM, Dean Pullen
On 10/29/2010 4:33 PM, Shawn Heisey wrote:
The recommended method of safely upgrading Solr that I've read about
is to upgrade slave servers, keeping your production application
pointed either at another set of slave servers or your master
servers. Then you test it with a dev copy of your
On 10/27/2010 8:34 PM, Shawn Heisey wrote:
I started to upgrade my slave servers from 1.4.1 to 3.1-dev checked
out this morning. Because of SOLR-2034 (new javabin version) the
replication fails.
Asking about it in comments on SOLR-2034 brought up the suggestion of
switching to XML instead
I started to upgrade my slave servers from 1.4.1 to 3.1-dev checked out
this morning. Because of SOLR-2034 (new javabin version) the
replication fails.
Asking about it in comments on SOLR-2034 brought up the suggestion of
switching to XML instead of javabin, but so far I have not been able
34 matches
Mail list logo