Hello,
We are needing a recommendation for solr replication throttling. What are your
recommendations for maxWriteMBPerSec value? Our indexes contain 18 locales and
size for all indexes is 188GB and growing.
Also will replication throttling work with solr 4.10.3?
Thanks,
Pino Alu | HCL
, January 07, 2019 11:10 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Solr Replication
>
> In SolrCloud there are Data Centers.
> Your Cluster 1 is DataCenter 1 and your Cluster 2 is Data Center 2.
> You can then use CDCR (Cross Data Center Replication).
> http://lucene.a
In SolrCloud there are Data Centers.
Your Cluster 1 is DataCenter 1 and your Cluster 2 is Data Center 2.
You can then use CDCR (Cross Data Center Replication).
http://lucene.apache.org/solr/guide/7_0/cross-data-center-replication-cdcr.html
Nevertheless I would spend your Cluster 2 another 2
Hi All,
I would like to configure master slave between two solr cloud clusters (for
failover). Below is the scenario
Solr version : 7.0
Cluster 1:
3 zookeeper instances : zk1, zk2, zk3
2 solr instances : solr1, solr2
Cluster 2:
1 zookeeper instance : bkpzk1,
1 solr instances : bkpsolr1,
8 1:49 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Solr Replication being flaky (6.2.0)
>
> On 1/19/2018 11:27 AM, Shawn Heisey wrote:
>> On 1/19/2018 8:54 AM, Pouliot, Scott wrote:
>>> I do have a ticket in with our systems team to up the file handlers
>>>
Heisey [mailto:apa...@elyograg.org]
Sent: Friday, January 19, 2018 1:49 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr Replication being flaky (6.2.0)
On 1/19/2018 11:27 AM, Shawn Heisey wrote:
> On 1/19/2018 8:54 AM, Pouliot, Scott wrote:
>> I do have a ticket in with our sys
On 1/19/2018 11:27 AM, Shawn Heisey wrote:
On 1/19/2018 8:54 AM, Pouliot, Scott wrote:
I do have a ticket in with our systems team to up the file handlers
since I am seeing the "Too many files open" error on occasion on our
prod servers. Is this the setting you're referring to? Found we were
On 1/19/2018 8:54 AM, Pouliot, Scott wrote:
I do have a ticket in with our systems team to up the file handlers since I am seeing the "Too
many files open" error on occasion on our prod servers. Is this the setting you're referring
to? Found we were set to to 1024 using the "Ulimit" command.
ct: Re: Solr Replication being flaky (6.2.0)
"Could be", certainly. "Definitely is" is iffier ;)...
But the statement "If we restart the Solr service or optimize the core it seems
to kick back in again.", especially the "optimize" bit (which, by the way
Solr itself seems
> to be working like a champ, except when things get out of sync.
>
> Scott
>
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Friday, January 19, 2018 12:27 PM
> To: solr-user <solr-user@lucene.apache.
<solr-user@lucene.apache.org>
Subject: Re: Solr Replication being flaky (6.2.0)
Scott:
We usually recommend setting files and processes very, very high. Like 65K
high. Or unlimited if you can.
Plus max user processes should also be bumped very high as well, like 65K as
well.
Plus max
on on our prod servers.
> Is this the setting you're referring to? Found we were set to to 1024 using
> the "Ulimit" command.
>
> -Original Message-
> From: Shawn Heisey [mailto:apa...@elyograg.org]
> Sent: Friday, January 19, 2018 10:48 AM
> To: solr-user@lu
age-
From: Shawn Heisey [mailto:apa...@elyograg.org]
Sent: Friday, January 19, 2018 10:48 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr Replication being flaky (6.2.0)
On 1/19/2018 7:50 AM, Pouliot, Scott wrote:
> So we're running Solr in a Master/Slave configuration (1 o
On 1/19/2018 7:50 AM, Pouliot, Scott wrote:
So we're running Solr in a Master/Slave configuration (1 of each) and it seems
that the replication stalls or stops functioning every now and again. If we
restart the Solr service or optimize the core it seems to kick back in again.
Anyone have any
Message-
From: David Hastings [mailto:hastings.recurs...@gmail.com]
Sent: Friday, January 19, 2018 10:35 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr Replication being flaky (6.2.0)
This happens to me quite often as well. Generally on the replication admin
screen it will say its
This happens to me quite often as well. Generally on the replication admin
screen it will say its downloading a file, but be at 0 or a VERY small
kb/sec. Then after a restart of the slave its back to downloading at 30 to
100 mg/sec. Would be curious if there actually is a solution to this aside
So we're running Solr in a Master/Slave configuration (1 of each) and it seems
that the replication stalls or stops functioning every now and again. If we
restart the Solr service or optimize the core it seems to kick back in again.
Anyone have any idea what might be causing this? We do have
Need some inputs or help in resolving replication across solr nodes. We
have installed Solr 6.5 in cloud mode and have 3 ZooKeepers and 2 Solr nodes
configured. Enabled Solr replication in my Solrj client but the replication
fails and is unable to create a collection.
>
> The s
. We have
> installed Solr 6.5 in cloud mode and have 3 ZooKeepers and 2 Solr nodes
> configured. Enabled Solr replication in my Solrj client but the replication
> fails and is unable to create a collection.
>
> The same code works in our different environment where in I have 1
Need some inputs or help in resolving replication across solr nodes. We have
installed Solr 6.5 in cloud mode and have 3 ZooKeepers and 2 Solr nodes
configured. Enabled Solr replication in my Solrj client but the replication
fails and is unable to create a collection.
The same code works
Hi,
I have a solr replication set up from master to slave in legacy ( It's not from
the solr cloud).
Somehow the first initial replication doesn't finish and when it reaches 99%
and got the error as following and then restart from the beginning.
I don't know why it is keep retriggering
Hi,
We try to set up a SOLR Cloud environment using 1 shard with 2
replicas (1 leader). The replicas are managed by 3 zookeeper
instances.
The setup seems fine when we do the normal work. The data is being
replicated at runtime.
Now we try to simulate erroneous behavior in several cases:
Turn
in context:
http://lucene.472066.n3.nabble.com/Solr-Replication-error-tp4252929.html
Sent from the Solr - User mailing list archive at Nabble.com.
I bet you have the admin UI open on your second slave. The _=144... is
the give-away. Those requests are the admin UI asking the replication
handler for the status of replication.
Upayavira
On Wed, Sep 9, 2015, at 06:32 AM, Kamal Kishore Aggarwal wrote:
> Hi Team,
>
> I am currently working
Hello,
I'd say opposite: high load causes long time to respond. 'command=details'
is rather cheap and fast _I believe_.
On Mon, Sep 14, 2015 at 10:20 AM, Kamal Kishore Aggarwal <
kkroyal@gmail.com> wrote:
> Can anybody suggest me something..
>
> On Wed, Sep 9, 2015 at 11:02 AM, Kamal
Can anybody suggest me something..
On Wed, Sep 9, 2015 at 11:02 AM, Kamal Kishore Aggarwal <
kkroyal@gmail.com> wrote:
> Hi Team,
>
> I am currently working with Java-1.7, Solr-4.8.1 with tomcat 7. The solr
> configuration has master & slave ( 2 Slaves) architecture.
>
>
> Master & Slave 2
Hi Team,
I am currently working with Java-1.7, Solr-4.8.1 with tomcat 7. The solr
configuration has master & slave ( 2 Slaves) architecture.
Master & Slave 2 are in same server location (say zone A) , whereas Slave 1
is in another server in different zone (say zone B). There is latency of 40
ms
Hi,
This sounds quite strange. Do you see any error messages either in the solr
admin's replication page or in the master's OR slave's logs?
When we had issues with slave replicating from the master, they related to
slave running out of disk. I'm sure there could be a bunch of other reasons
for
Hi All,
My master and slave index version and generation is the same
yet the index is not in sync because when I execute the same query
on both master and slave I see old docs on slave which should not be there.
I also tried to fetch a specific indexversion on slave using
On 1/24/2015 10:56 PM, Dan Davis wrote:
When I polled the various projects already using Solr at my organization, I
was greatly surprised that none of them were using Solr replication,
because they had talked about replicating the data.
But we are not Pinterest, and do not expect
using Solr at my
organization, I
was greatly surprised that none of them were using Solr replication,
because they had talked about replicating the data.
But we are not Pinterest, and do not expect to be taking in changes
one
post at a time (at least the engineers don't
Davis wrote:
When I polled the various projects already using Solr at my
organization, I
was greatly surprised that none of them were using Solr replication,
because they had talked about replicating the data.
But we are not Pinterest, and do not expect to be taking in changes one
post
already using Solr at my
organization, I
was greatly surprised that none of them were using Solr replication,
because they had talked about replicating the data.
But we are not Pinterest, and do not expect to be taking in changes one
post at a time (at least the engineers don't
, Jan 25, 2015 at 9:26 AM, Shawn Heisey apa...@elyograg.org
javascript:; wrote:
On 1/24/2015 10:56 PM, Dan Davis wrote:
When I polled the various projects already using Solr at my
organization, I
was greatly surprised that none of them were using Solr replication,
because they had
When I polled the various projects already using Solr at my organization, I
was greatly surprised that none of them were using Solr replication,
because they had talked about replicating the data.
But we are not Pinterest, and do not expect to be taking in changes one
post at a time (at least
I haven't seen any activity regarding this in Jira, just curious if it
would be looked into anytime soon...
On Thu, Oct 2, 2014 at 10:11 AM, Phil Black-Knight
pblackkni...@globalgiving.org wrote:
see the ticket here:
https://issues.apache.org/jira/browse/SOLR-6579
including a patch to fix
I was helping to look into this with Nick I think we may have figured out
the core of the problem...
The problem is easily reproducible by starting replication on the slave and
then sending a shutdown command to tomcat (e.g. catalina.sh stop).
With a debugger attached, it looks like the
On 10/2/2014 7:25 AM, Phil Black-Knight wrote:
I was helping to look into this with Nick I think we may have figured out
the core of the problem...
The problem is easily reproducible by starting replication on the slave and
then sending a shutdown command to tomcat (e.g. catalina.sh stop).
see the ticket here:
https://issues.apache.org/jira/browse/SOLR-6579
including a patch to fix it.
On Thu, Oct 2, 2014 at 9:44 AM, Shawn Heisey apa...@elyograg.org wrote:
On 10/2/2014 7:25 AM, Phil Black-Knight wrote:
I was helping to look into this with Nick I think we may have figured
out
Hello,
I have solr 4.10 running on tomcat 7. I'm doing replication from one master
to about 10 slaves, with standard configuration:
requestHandler name=/replication class=solr.ReplicationHandler
lst name=master
str name=enable${enable.master:false}/str
Hi folks,
I'm using Solr 4.3.1 with a master/slave configuration.
Configuration:
Master:
* lst name=master*
* str name=replicateAftercommit/str*
* str name=replicateAfterstartup/str*
* str name=confFilesschema.xml,stopwords.txt/str*
* /lst*
Slave:
* lst
On 9/1/2014 10:31 AM, Mauricio Ferreyra wrote:
I'm using Solr 4.3.1 with a master/slave configuration.
Configuration:
Master:
* lst name=master*
* str name=replicateAftercommit/str*
* str name=replicateAfterstartup/str*
* str
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:
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
Hi,
I am using solr 4.4 , replication set with one Master and 1 slave. Master
is set to replicate after startup and commit. It has an internal autocommit
of maxTime:15000.
Slave polls the master every 45sec to check for updates.
I indexed Master with DIH,
First, indexed half million docs in
:8080_solr},
Can someone please tell me where do I tell zookeeper 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
Hi,
We are using solr 4.4 version and am facing some issue with replication,
we are trying to replicate very large index about 105G. Once the
replication is done, I see the index.timestamp directory but the index
directory is not present ? Why is this happening ?
Also, I see with every
that data anywhere except in
index).
--
View this message in context:
http://lucene.472066.n3.nabble.com/SOLR-replication-question-tp4081161.html
Sent from the Solr - User mailing list archive at Nabble.com.
I am currently using SOLR 4.4. but not planning to use solrcloud in very
near
future.
I have 3 master / 3 slave setup. Each master is linked to its
corresponding
slave.. I have disabled auto polling..
We do both push (using MQ) and pull indexing using SOLRJ indexing
program.
I have enabled
at first .
does solr 4 need to special config anything ?
thanks a lot .
--
View this message in context:
http://lucene.472066.n3.nabble.com/problems-about-solr-replication-in-4-3-tp4079665p4080480.html
Sent from the Solr - User mailing list archive at Nabble.com.
.nabble.com/problems-about-solr-replication-in-4-3-tp4079665p4080480.html
Sent from the Solr - User mailing list archive at Nabble.com.
during this process !
i am newer to solr 4 , does this normal ? any ideas , thanks !
--
View this message in context:
http://lucene.472066.n3.nabble.com/problems-about-solr-replication-in-4-3-tp4079665.html
Sent from the Solr - User mailing list archive at Nabble.com.
!
i am newer to solr 4 , does this normal ? any ideas , thanks !
--
View this message in context:
http://lucene.472066.n3.nabble.com/problems-about-solr-replication-in-4-3-tp4079665.html
Sent from the Solr - User mailing list archive at Nabble.com.
I agree. It is even slower when the slave is being pounded.
On Fri, Jun 21, 2013 at 3:35 AM, Ted zhanghailian...@qq.com wrote:
Solr replication is extremely slow(less then 1MB/s)
When the replication is runinng,network and disk occupancy rate remained at
a very low level.
I've tried
Solr replication is extremely slow(less then 1MB/s)
When the replication is runinng,network and disk occupancy rate remained at
a very low level.
I've tried downloading a piece of the index file with browser.
like this:
http://master/solr/product/replication?command=filecontentwt
: Also when I checked the solr log.
:
: [org.apache.solr.handler.SnapPuller] Master at:
: http://192.168.2.204:8080/solr/replication is not available. Index fetch
: failed. Exception: Connection refused
:
:
: BTW, I was able to fetch the replication file with wget directly.
Are you certian
Hi guys,
I have some problems with Solr replication and can see some
unexpected behavior.
Would be nice to have some answers where am I wrong, or what is the best
way to solve the problem.
I have a replication master-slave. http://192.168.2.204:8080/solr/ is
master and http://192.168.2.174:8080
Hi guys,
I have some problems with Solr replication and can see some
unexpected behavior.
Would be nice to have some answers where am I wrong, or what is the best
way to solve the problem.
I have a replication master-slave. http://192.168.2.204:8080/solr/ is
master and http://192.168.2.174:8080
Hey,
Currently we are using solr 4.0 with a master slave setup. The data gets
indexed on the master and then we issue a fetchindex command to replicate
it on the slave. The slave has a postCommit listener which gets kicked off
when replication finishes and we depend on this listener to know whn
On Mar 21, 2013, at 12:08 PM, Rohit Harchandani rhar...@gmail.com wrote:
Hey,
Currently we are using solr 4.0 with a master slave setup. The data gets
indexed on the master and then we issue a fetchindex command to replicate
it on the slave. The slave has a postCommit listener which gets
Thanks for the info.
I understand that the latest replicateable version of index may
differ from the actual version of index on master/slave.
But why when I use
/solr/replication?command=indexversion
On master:
response
lst name=responseHeader
int name=status0/int
int name=QTime0/int
/lst
long
that the latest replicateable version of index may
differ from the actual version of index on master/slave.
But why when I use
/solr/replication?command=indexversion
On master:
response
lst name=responseHeader
int name=status0/int
int name=QTime0/int
/lst
long name
Radecki radecki.ra...@gmail.com wrote:
Thanks for the info.
I understand that the latest replicateable version of index may
differ from the actual version of index on master/slave.
But why when I use
/solr/replication?command=indexversion
On master:
response
lst name=responseHeader
int name
/jira/browse/SOLR-3681
: Date: Fri, 15 Mar 2013 11:43:05 +0100
: From: Rafał Radecki radecki.ra...@gmail.com
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: Re: Solr 4.1 monitoring with /solr/replication?command=details -
: indexVersion?
:
: I use http
On Mar 15, 2013, at 6:43 AM, Rafał Radecki radecki.ra...@gmail.com wrote:
I use http and get /solr/replication?command=indexversion urls to get
index versions on master and slave. The replication works fine but
index versions from /solr/replication?command=indexversion differ.
I think thats
my backup will be corrupted. Can
you please suggest if there is a cleaner way to handle this
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Replication-tp4047266p4047591.html
Sent from the Solr - User mailing list archive at Nabble.com.
I use http and get /solr/replication?command=indexversion urls to get
index versions on master and slave. The replication works fine but
index versions from /solr/replication?command=indexversion differ.
Best regards,
Rafal.
2013/3/14 Mark Miller markrmil...@gmail.com:
What calls are you using
data from
master core without firing a commit operation on that core
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Replication-tp4047266.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi Vicky,
May be str name=replicateAfterstartup/str ?
For backups http://master_host:port/solr/replication?command=backup would be
more suitable.
or str name=backupAfterstartup/str
--- On Thu, 3/14/13, vicky desai vicky.de...@germinait.com wrote:
From: vicky desai vicky.de
Hi All.
I am monitoring two solr 4.1 solr instances in master-slave setup. On
both nodes I check url /solr/replication?command=details and parse it
to get:
- on master: if replication is enabled - field replicationEnabled
- on slave: if replication is enabled - field replicationEnabled
- on slave
In the output of:
/solr/replication?command=details
there is indexVersion mentioned many times:
response
lst name=responseHeader
int name=status0/int
int name=QTime3/int
/lst
lst name=details
str name=indexSize22.59 KB/str
str name=indexPath/usr/share/solr/data/index//str
arr name=commits
lst
On Mar 14, 2013, at 8:10 AM, Rafał Radecki radecki.ra...@gmail.com wrote:
Is this a bug?
Yes, 4.1 had some replication issues just as you seem to describe here. It all
should be fixed in 4.2 which is available now and is a simple upgrade.
- Mark
1,022.31 MB
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-4-1-monitoring-with-solr-replication-command-details-indexVersion-tp4047329p4047380.html
Sent from the Solr - User mailing list archive at Nabble.com.
:
1363272681951
93
1,022.31 MB
Slave:
1363273274085
95
1,022.31 MB
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-4-1-monitoring-with-solr-replication-command-details-indexVersion-tp4047329p4047380.html
Sent from the Solr - User mailing list archive
this
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Replication-tp4047266p4047591.html
Sent from the Solr - User mailing list archive at Nabble.com.
in context:
http://lucene.472066.n3.nabble.com/Solr-replication-takes-long-time-tp4046388p4046951.html
Sent from the Solr - User mailing list archive at Nabble.com.
. But for now, the 2 slaves can handle with no problems
all the queries.
Regards,
Victor
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-replication-takes-long-time-tp4046388p4046993.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi guys,
I have a problem with Solr replication. I have 2 solr servers (Solr 4.0.0) 1
master and 1 slave (8 processors,16GB RAM ,Ubuntu 11, ext3, each). In
every server, there are 2 independent instances of solr running (I tried
also multicore config, but having independent instances has for me
Are you using Solr 4.1?
- Mark
On Mar 11, 2013, at 1:53 PM, Victor Ruiz bik1...@gmail.com wrote:
Hi guys,
I have a problem with Solr replication. I have 2 solr servers (Solr 4.0.0) 1
master and 1 slave (8 processors,16GB RAM ,Ubuntu 11, ext3, each). In
every server, there are 2
a problem with Solr replication. I have 2 solr servers (Solr
4.0.0) 1
master and 1 slave (8 processors,16GB RAM ,Ubuntu 11, ext3, each). In
every server, there are 2 independent instances of solr running (I tried
also multicore config, but having independent instances has for me better
performance
, 2013, at 1:53 PM, Victor Ruiz lt;
bik1979@
gt; wrote:
Hi guys,
I have a problem with Solr replication. I have 2 solr servers (Solr
4.0.0) 1
master and 1 slave (8 processors,16GB RAM ,Ubuntu 11, ext3, each). In
every server, there are 2 independent instances of solr running (I tried
decided not to try it for now
Mark Miller-3 wrote
Are you using Solr 4.1?
- Mark
On Mar 11, 2013, at 1:53 PM, Victor Ruiz lt;
bik1979@
gt; wrote:
Hi guys,
I have a problem with Solr replication. I have 2 solr servers (Solr
4.0.0) 1
master and 1 slave (8 processors,16GB RAM
:16 PM, Lance Norskog goks...@gmail.com
wrote:
Maybe these are text encoding markers?
- Original Message -
| From: Eva Lacy e...@lacy.ie
| To: solr-user@lucene.apache.org
| Sent: Thursday, November 29, 2012 3:53:07 AM
| Subject: Re: Downloading files from the solr
, November 29, 2012 3:53:07 AM
| Subject: Re: Downloading files from the solr replication Handler
|
| I tried downloading them with my browser and also with a c#
| WebRequest.
| If I skip the first and last 4 bytes it seems work fine.
|
|
| On Thu, Nov 29, 2012 at 2:28 AM, Erick Erickson
@lucene.apache.org
| Sent: Thursday, November 29, 2012 3:53:07 AM
| Subject: Re: Downloading files from the solr replication Handler
|
| I tried downloading them with my browser and also with a c#
| WebRequest.
| If I skip the first and last 4 bytes it seems work fine.
|
|
| On Thu, Nov 29
: Downloading files from the solr replication Handler
|
| I tried downloading them with my browser and also with a c#
| WebRequest.
| If I skip the first and last 4 bytes it seems work fine.
|
|
| On Thu, Nov 29, 2012 at 2:28 AM, Erick Erickson
| erickerick...@gmail.comwrote:
|
| How
I tried downloading them with my browser and also with a c# WebRequest.
If I skip the first and last 4 bytes it seems work fine.
On Thu, Nov 29, 2012 at 2:28 AM, Erick Erickson erickerick...@gmail.comwrote:
How are you downloading them? I suspect the issue is
with the download process rather
Maybe these are text encoding markers?
- Original Message -
| From: Eva Lacy e...@lacy.ie
| To: solr-user@lucene.apache.org
| Sent: Thursday, November 29, 2012 3:53:07 AM
| Subject: Re: Downloading files from the solr replication Handler
|
| I tried downloading them with my browser
I downloaded some configuration and data files directly from solr in an
attempt to develop a backup solution.
I noticed there is some characters at the start and end of the file that
aren't in configuration files, I notice the same characters at the start
and end of the data files.
Anyone with any
Just to add to that, I'm using solr 3.6.1
On Wed, Nov 28, 2012 at 5:18 PM, Eva Lacy e...@lacy.ie wrote:
I downloaded some configuration and data files directly from solr in an
attempt to develop a backup solution.
I noticed there is some characters at the start and end of the file that
How are you downloading them? I suspect the issue is
with the download process rather than Solr, but I'm just guessing.
Best
Erick
On Wed, Nov 28, 2012 at 12:19 PM, Eva Lacy e...@lacy.ie wrote:
Just to add to that, I'm using solr 3.6.1
On Wed, Nov 28, 2012 at 5:18 PM, Eva Lacy e...@lacy.ie
bad, but I don't know the intern
mecanisms.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-replication-tp4021875p4022314.html
Sent from the Solr - User mailing list archive at Nabble.com.
can happend in this configuration?
With tests, I can't see nothing bad, but I don't know the intern mecanisms.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-replication-tp4021875p4022314.html
Sent from the Solr - User mailing list archive at Nabble.com.
in this configuration?
With tests, I can't see nothing bad, but I don't know the intern mecanisms.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-replication-tp4021875p4022314.html
Sent from the Solr - User mailing list archive at Nabble.com.
in context:
http://lucene.472066.n3.nabble.com/Solr-replication-tp4021875.html
Sent from the Solr - User mailing list archive at Nabble.com.
... Calissa yapar...
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Replication-is-not-Possible-on-RAMDirectory-tp4017766p4018670.html
Sent from the Solr - User mailing list archive at Nabble.com.
pushing from
master to replica/slave... so why it is not possible to push from RAM to
HDD? If my logic is wrong, someone can please explain me all these?
-
Zeki ama calismiyor... Calissa yapar...
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Replication
there are mostly 16 or 32mb cache disks around (or i am checking
the wrong stuff? ) if so, that amount definitely too small...
-
Zeki ama calismiyor... Calissa yapar...
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Replication-is-not-Possible-on-RAMDirectory
Shawn Heisey-4 wrote
... transparently mapping the files on disk to a virtual memory space
and
using excess RAM to cache that data and make it fast. If you have
enough extra memory (disk cache) to fit the entire index, the OS will
never have to read any part of the index from disk more
not wrong there are mostly 16 or 32mb cache disks around (or i am checking
the wrong stuff? ) if so, that amount definitely too small...
-
Zeki ama calismiyor... Calissa yapar...
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Replication-is-not-Possible
1 - 100 of 230 matches
Mail list logo
