On 1/14/2019 3:18 PM, Audun Holme wrote:
So I have read about solr and think maybe I need solr.
I found this link:https://github.com/integer-net/solr-magento1
I downloaed that plugin and started to read about how to install it. Unsure as
I was I sent an email to https://integernet-solr.com/ to a
Hi
My magento store (magento 1.9.3.7) have a very slow search, takes 30 seconds to
show some results, should be down to 1 second...
So I have read about solr and think maybe I need solr.
I found this link:https://github.com/integer-net/solr-magento1
I downloaed that plugin and started to read abou
To chime in, in certain cases the memory requirements for 4x (and 5x) are _much_
improved, see:
https://lucidworks.com/blog/2012/04/06/memory-comparisons-between-solr-3x-and-trunk/
But as Shawn says, it's not a magic bullet.
Solr 5 requires Java 7, so that's one thing to be aware of. Plus, you
e
On 10/21/2015 12:41 PM, Robert Hume wrote:
> I've inherited a project that uses a Solr 3.6.0 deployment. (Several
> masters and several slaves – I think there are 6 Solr instances in total.)
>
> I've been tasked with investigating if upgrading our 3.6.0 deployment will
> improve performance – the
Hello, I'm hoping to get some quick advice from the Solr gurus out there ...
I’ve inherited a project that uses a Solr 3.6.0 deployment. (Several
masters and several slaves – I think there are 6 Solr instances in total.)
I’ve been tasked with investigating if upgrading our 3.6.0 deployment
s to be queried on based on
> > the time ranged in the query. Cores that fall off the 60 day range are
> > deleted through solr's RESTful API.
> >
> > This all sounds a lot like what Solr Cloud provides, so I started looking
> > at Solr Cloud's features.
>
fall off the 60 day range are
> deleted through solr's RESTful API.
>
> This all sounds a lot like what Solr Cloud provides, so I started looking
> at Solr Cloud's features.
>
> My newbie questions:
>
> - it looks like the way to write a document is to pick a node
ng
at Solr Cloud's features.
My newbie questions:
- it looks like the way to write a document is to pick a node (possibly
using a LB), send it to that node, and let solr figure out which nodes that
document is supposed to go. is this the recommended way?
- similarly, can I just randomly p
Hi,
In your Solr version there is a notion of Searcher being opened and
reopened. Every time that happens those non-cumulative stats reset. The
cumulative_ stats just don't refresh, so you have numbers from when the
whole Solr started, not just from the last time Searcher opened.
Your cache is
Sorry, I did search for an answer, but didn't find an applicable one.
I'm currently stuck on 1.4.1 (running in Tomcat 6 on 64bit Linux) for
the time being...
When I see stats like this:
name: documentCache
class: org.apache.solr.search.LRUCache
version: 1.0
description: LRU
Hello!
I just started using Solr. My general use case is pushing a lot of data from
Hbase to solr via an M/R job using Solrj. I have lots of questions, but the
ones I'd like to start with are:
(1)
I noticed this:
http://lucene.472066.n3.nabble.com/what-happens-to-docsPending-if-stop-solr-befor
: 1. It seems that Solr creates/searches one big index, at least logically
: - for the current release, does it ever create multiple smaller indexes
: behind the scene (except for the secondary, temporary ones used for
: update)?
Solr only creates one physical lucene index on disk.
: 2. The snaps
Hi,
I have a few general questions:
1. It seems that Solr creates/searches one big index, at least logically - for
the current release, does it ever create multiple smaller indexes behind the
scene (except for the secondary, temporary ones used for update)?
2. The snapshooter makes a "complete"
13 matches
Mail list logo
