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
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
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
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
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
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
, when it
comes to configuring
Please let me know how I can use the same encrypted password as in
Security.json when setting up Master/Slave Replication for Solr.
At the moment, the cleartext password is the only way it can be configured.
It is not possible to use the same string that goes in
/Slave Index Replication Strategy,
the slave config requires to give the
BasicAuthentication password in plain text? Is it something I got wrong? But
in my setup of HA with Master/Slave replication it works in this manner.
https://lucene.apache.org/solr/guide/7_2/index-replication.html this also
Done https://issues.apache.org/jira/browse/SOLR-11938.
Thanks!
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
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 m
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
So you say that master/slave replication takes up to 20 seconds but it
takes 8-10 minutes just to copy the entire index?
Solr is _already_ speeding up your copy enormously by just copying
changed segments. There's nothing magic you can do to make it faster.
And if your master happens to
Erick,
when we copy entire index it takes 8- 10 mins .
On Wed, Jun 28, 2017 at 9:22 PM, Erick Erickson
wrote:
> How long it takes to copy the entire index from one machine to another
> over your network. Solr can't go any faster than your network can
> support. Consider SolrCloud if you need s
How long it takes to copy the entire index from one machine to another
over your network. Solr can't go any faster than your network can
support. Consider SolrCloud if you need something closer to NRT.
Best,
Erick
On Tue, Jun 27, 2017 at 11:31 PM, Midas A wrote:
> Hi,
>
> we have around 2000
Hi,
we have around 2000 documents and our master to slave replication is
taking time upto 20 second.
What should i check ?
@lucene.apache.org
Subject: RE: SOLR 4.8.0 Master/Slave Replication Issues
Valid point on the soft commits. I'll try disabling them to see if there if
any change in performance as well. Worth a shot ;-)
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
l Message-
> From: Andrea Gazzarini [mailto:gxs...@gmail.com]
> Sent: Friday, March 10, 2017 3:12 AM
> To: solr-user@lucene.apache.org
> Subject: Re: SOLR 4.8.0 Master/Slave Replication Issues
>
> Hi Scott,
> that could depend on a lot of things. Some questions:
>
>
. Hoping this might be our issue ;-) I'll report back in a
> bit though!
>
> Thanks for the reminder about commits. We may have forgotten to change these
> values when these new servers got setup.
>
> Scott
>
> -Original Message-
> From: Andrea Gazzarini [
se
values when these new servers got setup.
Scott
-Original Message-
From: Andrea Gazzarini [mailto:gxs...@gmail.com]
Sent: Friday, March 10, 2017 3:12 AM
To: solr-user@lucene.apache.org
Subject: Re: SOLR 4.8.0 Master/Slave Replication Issues
Hi Scott,
that could depend on a lot
Hi Scott,
that could depend on a lot of things. Some questions:
* What is your commit policy? Explicit / auto / soft / hard ...
* "Other days things are off by a small amount between master and
slave"...what do you mean exactly? What is the behaviour you see in
terms of index versions bet
So we've been having oddball replication issues between master and slave (Not
SOLRCloud) for a few weeks now. Some days...everything lines up just fine.
Other days things are off by a small amount between master and slave.
Here is the config on the MASTER server replication config:
w index writer
gets the write lock, but we really don't want that fixed! ;)
Thanks again,
Jeremy
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: 22 November 2016 18:37
To: solr-user
Subject: Re: Partial replication blocks subsequent requests when using
This sounds a lot like:
https://issues.apache.org/jira/browse/SOLR-9706
Could you attach your patch to that issue if you think it's the same?
And please copy/paste your e-mail in a comment if you would, you've
obviously done more research on the cause than I did and that'd save
some work wheneve
Hi All,
We're running a fairly non-standard solr configuration. We ingest into named
shards in master cores and then replicate out to slaves running solr cloud. So
in effect we are using solrcloud only to manage the config files and more
importantly to look after the cluster state. Our corpu
On 9/6/2016 1:51 AM, Georg Sorst wrote:
> So if there is a lastmodified timestamp, it would be trivial to see which
> config files have been updated in the meantime. Any idea why the
> replication relies on an update to the index then?
Master-slave replication was designed to copy an i
ex replication if
> (and only if) the
> index on the master has changed.
>
In the documentation for the master-slave replication it says:
> The slave issues a filelist command to get the list of the files. This
command returns the names of the files as well as some metadata (for
example, s
> How can I get the Query Elevation component to play nice with Master-Slave
> replication? So far I've tried:
>
> * Manually calling commit() after updating the elevate.xml (that's seems to
> be no-op when the index hasn't changed: "No uncommitted changes. Skippin
y allows
configuration during runtime, ie. without changing the index, by just
modifying the config.
How can I get the Query Elevation component to play nice with Master-Slave
replication? So far I've tried:
* Manually calling commit() after updating the elevate.xml (that's seems to
be no
Hello
I have 14 cores, with a couple of them using Shards and now I am looking at
the master/Slave fallback solution. Can anyone please point me in the right
direction to get started?
Thanks
Kalpana
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-5-4-1-Master-Slave
I'll give that a shot, thanks!
On Wed, Jul 3, 2013 at 12:28 PM, Shawn Heisey wrote:
> On 7/3/2013 9:29 AM, Neal Ensor wrote:
>
>> Posted the solr config up as http://apaste.info/4eKC (hope that works).
>> Note that this is largely a hold-over from upgrades of previous solr
>> versions, there
On 7/3/2013 9:29 AM, Neal Ensor wrote:
Posted the solr config up as http://apaste.info/4eKC (hope that works).
Note that this is largely a hold-over from upgrades of previous solr
versions, there may be lots of cruft left over. If it's advisable to do
so, I would certainly be open to starting
Posted the solr config up as http://apaste.info/4eKC (hope that works).
Note that this is largely a hold-over from upgrades of previous solr
versions, there may be lots of cruft left over. If it's advisable to do
so, I would certainly be open to starting from scratch with a 4.3+ example
configura
On 7/1/2013 1:07 PM, Neal Ensor wrote:
is it conceivable that there's too much traffic, causing Solr to stall
re-opening the searcher (thus releasing to the new index)? I'm grasping at
straws, and this is beginning to bug me a lot. The traffic logs wouldn't
seem to support this (apart from peri
is it conceivable that there's too much traffic, causing Solr to stall
re-opening the searcher (thus releasing to the new index)? I'm grasping at
straws, and this is beginning to bug me a lot. The traffic logs wouldn't
seem to support this (apart from periodic health-check pings, the load is
dist
Odd - looks like it's stuck waiting to be notified that a new searcher is ready.
- Mark
On Jun 27, 2013, at 8:58 AM, Neal Ensor wrote:
> Okay, I have done this (updated to 4.3.1 across master and four slaves; one
> of these is my own PC for experiments, it is not being accessed by clients).
>
Okay, I have done this (updated to 4.3.1 across master and four slaves; one
of these is my own PC for experiments, it is not being accessed by clients).
Just had a minor replication this morning, and all three slaves are "stuck"
again. Replication supposedly started at 8:40, ended 30 seconds late
A bunch of replication related issues were fixed in 4.2.1 so you're
better off upgrading to 4.2.1 or later (4.3.1 is the latest release).
On Mon, Jun 24, 2013 at 6:55 PM, Neal Ensor wrote:
> As a bit of background, we run a setup (coming from 3.6.1 to 4.2 relatively
> recently) with a single mast
As a bit of background, we run a setup (coming from 3.6.1 to 4.2 relatively
recently) with a single master receiving updates with three slaves pulling
changes in. Our index is around 5 million documents, around 26GB in size
total.
The situation I'm seeing is this: occasionally we update the mast
:(
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-vs-Solr-master-slave-replication-tp4055541p4056926.html
Sent from the Solr - User mailing list archive at Nabble.com.
Also, I forgot to say... the same error started to happen again.. the index
is again corrupted :(
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-vs-Solr-master-slave-replication-tp4055541p4056926.html
Sent from the Solr - User mailing list archive at Nabble.com.
ext:
http://lucene.472066.n3.nabble.com/SolrCloud-vs-Solr-master-slave-replication-tp4055541p4056925.html
Sent from the Solr - User mailing list archive at Nabble.com.
On 4/17/2013 1:20 AM, Maciej Pestka wrote:
Hi,
I've configured basic authentication on tomcat & my slave solr instance and it
works.
Any idea how to configure slave to replicate properly with digest
authentication?
on Solr WIKI I could find only basic authentication example:
http://wiki.apach
On 4/15/2013 3:38 AM, Victor Ruiz wrote:
About SolrCloud, I know it doesn't use master-slave replication, but
incremental updates, item by item. That's why I thought it could work for
us, since our bottleneck appear to be the replication cycles. But another
point is, if the indexing
ave also a bad effect on the performance. Apart of the
RAM used by JVM, the server has more than 10GB of unused RAM, which should
be enough to cache the index.
About SolrCloud, I know it doesn't use master-slave replication, but
incremental updates, item by item. That's why I thought
On 4/12/2013 6:45 AM, Victor Ruiz wrote:
As you can read, at the end it was due to a fail in the Solr master-slave
replication, and now I don't know if we should think about migrating to
SolrCloud, since Solr master-slave replications seems not to fit to our
requirements:
* index size:
https://issues.apache.org/jira/browse/SOLR-4707
As you can read, at the end it was due to a fail in the Solr master-slave
replication, and now I don't know if we should think about migrating to
SolrCloud, since Solr master-slave replications seems not to fit to our
requirements:
* index size: ~20 million
. I end up with just the "index" directory
after replication is complete.
I'm using Tomcat/Solr 4.1
-Original Message-
From: adityab [mailto:aditya_ba...@yahoo.com]
Sent: Wednesday, February 27, 2013 12:22 PM
To: solr-user@lucene.apache.org
Subject: RE: Solr 4.1 Master ->
ssage in context:
http://lucene.472066.n3.nabble.com/Solr-4-1-Master-Slave-Replication-Issues-and-Solr-4-2-tp4043403p4043426.html
Sent from the Solr - User mailing list archive at Nabble.com.
nd for me. I
stopped solr, renamed index. folder to just index and modified
index.properties file to use the index folder.
#index.properties
#Thu Feb 21 02:29:09 CST 2013
#index=index.20130221022400014
index=index
master->slave replication seemed to behave as expected after this change f
On Feb 27, 2013, at 10:51 AM, Michael Della Bitta
wrote:
> Are there any temporary fixes to this problem aside from waiting for 4.2?
Not really. I guess my advice would be this:
If you use SolrCloud or single node, don't worry, this doesn't affect you.
If you use 4.1
Isn’t a Game
On Wed, Feb 27, 2013 at 10:43 AM, Mark Miller wrote:
> FYI
>
> There have been a couple issues discovered around master->slave replication
> with Solr 4.1.
>
> The biggest issue tends to be that a full replication is triggered every time
> the slave polls the
Oh yeah, forgot to mention. This is just for master-slave replication - these
issues don't affect SolrCloud's use of replication.
- Mark
On Feb 27, 2013, at 10:43 AM, Mark Miller wrote:
> FYI
>
> There have been a couple issues discovered around master->slave replic
FYI
There have been a couple issues discovered around master->slave replication
with Solr 4.1.
The biggest issue tends to be that a full replication is triggered every time
the slave polls the master, even if this is not needed.
I'm out of my home base next week, but I plan on he
"Will traffic be served with a non "warmed" index searcher at any
point"
No. That's what auto-warming is all about.
More correctly, it depends on how you configure things in
your config file. There are entries like "firstSearcher",
"newSearcher" and various "autowarm" counts, all of which
you set
Correction: Will traffic be served with a non "warmed" index searcher at any
point?
Thanks,
Mike
On Mon, Aug 29, 2011 at 4:52 PM, Mike Austin wrote:
> "Distribution/Replication gives you a 'new' index on the slave. When Solr
> is told to use the new index, the old caches have to be discarded al
"Distribution/Replication gives you a 'new' index on the slave. When Solr is
told to use the new index, the old caches have to be discarded along with
the old Index Searcher. That's when autowarming occurs. If the current
Index Searcher is serving requests and when a new searcher is opened, the
ne
it's always been my understanding that the caches are discarded, then
rebuilt/warmed:
http://wiki.apache.org/solr/SolrCaching#Caching_and_Distribution.2BAC8-Replication
hth,
rob
On Mon, Aug 29, 2011 at 5:30 PM, Mike Austin wrote:
> How does warming work when a collection is being distribu
How does warming work when a collection is being distributed to a slave. I
understand that a temp directory is created and it is eventually copied to
the live folder, but what happens to the cache that was built in with the
old index? Does the cache get rebuilt, can we warm it before it becomes
l
f you have more than one slave so you can move things around while the
>>> remaining slave is reconfigured (or whatever)
>>>
>>> Best
>>> Erick
>>>
>>> On Mon, Jun 20, 2011 at 8:28 AM, Mark Schoy wrote:
>>>> Hi,
>>>>
>>>> if I use a master slave replication in Solr Cloud and the master
>>>> crashes, can the slave automatically switch to master mode?
>>>>
>>>> Or is there another way to index documents after the master is down?
>>>>
>>>> Thanks.
>>>>
>>>
>>
>
h).
>>
>> The fun part is continuing to serve requests while all this is going
>> on. It's easier
>> if you have more than one slave so you can move things around while the
>> remaining slave is reconfigured (or whatever)....
>>
>> Best
>> Erick
&
le all this is going
> on. It's easier
> if you have more than one slave so you can move things around while the
> remaining slave is reconfigured (or whatever)
>
> Best
> Erick
>
> On Mon, Jun 20, 2011 at 8:28 AM, Mark Schoy wrote:
>> Hi,
>>
>>
n 20, 2011 at 8:28 AM, Mark Schoy wrote:
> Hi,
>
> if I use a master slave replication in Solr Cloud and the master
> crashes, can the slave automatically switch to master mode?
>
> Or is there another way to index documents after the master is down?
>
> Thanks.
>
Hi,
if I use a master slave replication in Solr Cloud and the master
crashes, can the slave automatically switch to master mode?
Or is there another way to index documents after the master is down?
Thanks.
any attribute specified in solrcore.properties can be referenced in
solrconfig.xml/schema.xml. this has nothing specific with replication.
On Fri, Aug 28, 2009 at 8:19 AM, Ilan Rabinovitch wrote:
> Hello,
>
> I noticed the the documentation around Solr Replication in the wiki has
> recently change
Hello,
I noticed the the documentation around Solr Replication in the wiki has
recently changed to take Paul's patch into account (SOLR-1355).
I now see that with the current trunk of SOLR 1.4 it is possible to use
a single solrconfig.xml to define both master and slave configurations,
with
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
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
Hi Noble,
can these builds be used in production environment? Are they stable? we are
not going live now, but in a few months we will. as such when will 1.4 be
officially released?
2009/8/7 Noble Paul നോബിള് नोब्ळ्
> 1.4 is not released yet. you can grab a nightly from here
> http://people.apac
On Fri, Aug 7, 2009 at 12:47 PM, Ninad Raut wrote:
> Hi,
> I want to know how to setup master-slave configuration for Solr 1.3 . I
> can't get documentation on the net. I found one for 1.4 but not for 1.3 .
> ReplicationHandler is not present in 1.3.
> Also, I would like to know from will I get
1.4 is not released yet. you can grab a nightly from here
http://people.apache.org/builds/lucene/solr/nightly/
On Fri, Aug 7, 2009 at 12:47 PM, Ninad Raut wrote:
> Hi,
> I want to know how to setup master-slave configuration for Solr 1.3 . I
> can't get documentation on the net. I found one for
Hi,
I want to know how to setup master-slave configuration for Solr 1.3 . I
can't get documentation on the net. I found one for 1.4 but not for 1.3 .
ReplicationHandler is not present in 1.3.
Also, I would like to know from will I get the Solr 14. distribution. The
Solr Site lists mirrors only fo
: I want to know if we can use index replication when we have segmented indexes
: over multiple solr instances?
I'm not sure i understand your question, but a slave just knows about it's
master and the data in it -- it doesn't care or need to know if the master
index is really just a subset of
I want to know if we can use index replication when we have segmented indexes
over multiple solr instances?
--
View this message in context:
http://www.nabble.com/Master-Slave-Replication-tp16293553p16293553.html
Sent from the Solr - User mailing list archive at Nabble.com.
73 matches
Mail list logo
