Dear Folks,
We are using Solr 5.4.0 - "stand-alone" mode in our production boxes hosted
in Red Hat Enterprise Linux (RHEL) OS.
Each box have number of different cores. Have attached the screenshot shot
with the Solr core & system details.
1. Earlier indexing was performed every 30 minutes in bot
Please review:
http://wiki.apache.org/solr/UsingMailingLists
There isn't nearly enough information here to even begin to help. And have
you looked at the Solr logs for the replicas that are down to try to
diagnose the underlying issue?
Best,
Erick
On Fri, Aug 26, 2016 at 6:45 PM, Hardika Catur
There's no one right answer here. I've also seen a hybrid approach
where there are multiple collections each of which has some
number of tenants resident. Eventually, you need to think of some
kind of partitioning, my rough number of documents for a single core
is 50M (NOTE: I've seen between 10M a
On 8/26/2016 10:22 AM, D'agostino Victor wrote:
> Do you know in which version index format changes and if I should
> update to a higher version ?
In version 6.0, and again in the just-released 6.2, one aspect of the
index format has been updated. Version 6.1 didn't have any format
changes from 6
On 8/26/2016 1:13 PM, Chamil Jeewantha wrote:
> We are using SolrCloud as the search provider of a multi-tenant cloud based
> application. We have one schema for all the tenants. The indexes will have
> large number(millions) of documents.
>
> As of our research, we have two options,
>
>- One l
On 8/27/2016 9:08 AM, Thiru M wrote:
> We are using Solr 5.4.0 - "stand-alone" mode in our production boxes
> hosted in Red Hat Enterprise Linux (RHEL) OS.
>
> Each box have number of different cores. Have attached the screenshot
> shot with the Solr core & system details.
>
> 1. Earlier indexing w
On 8/25/2016 8:51 PM, Brent P wrote:
Replies inline. Hopefully they'll be easily visible.
> It will be writing documents at a rate of approximately 500 docs/second,
> and running search queries at about the same rate.
500 queries per second is a LOT. You're going to probably need a lot of
repl
On 8/26/2016 7:13 AM, Steven White wrote:
> But what about the current "default" list that comes with Solr? How was
> that list, for all supported languages, determined?
That list of stopwords was created from years of history with Lucene,
taking the expertise of many people and the wisdom of the
On 8/27/2016 12:39 PM, Shawn Heisey wrote:
> I personally think that stopword removal is more of a problem than a
> solution.
There actually is one thing that a stopword filter can dothat has little
to do with the purpose it was designed for. You can make it impossible
to search for certain words
In my own work, the risk to the business if every single client cannot
access search is so great, we would never consider putting everything in
one. You should certainly ask that question of the business stakeholders
before you decide.
For that reason, I might recommend that each of the multiple
Thank you everyone for your great support.
I will update you with our final approach.
Best regards,
Chamil
On Aug 28, 2016 01:34, "John Bickerstaff" wrote:
> In my own work, the risk to the business if every single client cannot
> access search is so great, we would never consider putting ever
11 matches
Mail list logo