Greetings, Apache Solr community.
I'm here to ask for your help and advice about a Solr-related problem I'm
having.
My company is an e-commerce website and uses Solr in production for the
querying of items in our inventory. The Solr installation was done by an
engineer who has left the company
We are using Solrj version 4.10.4 as the java client to add documents into
Solr version 1.4.1
Sample Pojo Object:
@SolrDocument(solrCoreName="customer")
public class Customer
{ private String customerId; private String customerName; private int age;
private List addresses; //getters and setters
I'm trying to debug why indexing in SolrCloud 7.1 is having so many issues. It
will hang most of the time, and timeout the rest.
Here's an example:
time curl -s 'myhost:8080/solr/mycollection/update/json/docs' -d
'{"solr_id":"test_001", "data_type":"test"}'|jq .
{
"responseHeader"
I've reproduced the issue and opened
https://issues.apache.org/jira/browse/SOLR-12020
-Yonik
On Thu, Feb 22, 2018 at 11:03 AM, Yonik Seeley wrote:
> Thanks Antelmo, I'm trying to reproduce this now.
> -Yonik
>
>
> On Mon, Feb 19, 2018 at 10:13 AM, Antelmo Aguilar wrote:
>> Hi all,
>>
>> I was
Dear Shawn,
Thanks a lot quick response.
I will check with the same.
Thanks & Regards
Fazulur Rehaman
On Wed, Feb 21, 2018 at 4:55 PM, Shawn Heisey wrote:
> On 2/21/2018 3:00 AM, Rehaman wrote:
>
>> We installed Ensembl server in our environment and not able to query
>> databases with large n
I managed to miss this reply earlier, but:
Shard: A logical segment of a collection
Replica: A physical core, representing a particular Shard
Replication Factor (RF): A set of Replicas, such that a single Replica exists
for each Shard in a Collection.
Availability Zone (AZ): A partitioned set o
I always filter solr request via a proxy (so solr itself is not exposed
directly to the web). In that proxy, the query parameters can be broken down
and filtered as desired (I examine authorities granted to a session to control
even which indexes are being searched) before passing the modified u
Hi,
I want to enable or disable a SolrFeature in LTR based on efi parameter.
In simple the query should be executed only if a parameter is true.
Any examples or suggestion on how to accomplish this?
Functions queries examples are are using fields to give a value to. In my
case I want to execute
On 2/22/2018 10:45 AM, LOPEZ-CORTES Mariano-ext wrote:
For the moment, I have the following information:
12GB is max java heap. Total memory i don't know. No direct access to host.
2 replicas =
Size 1 = 11.51 GB
Size 2 = 11.82 GB
(Sizes showed in the Core-Overview admin gui)
O
For the moment, I have the following information:
12GB is max java heap. Total memory i don't know. No direct access to host.
2 replicas =
Size 1 = 11.51 GB
Size 2 = 11.82 GB
(Sizes showed in the Core-Overview admin gui)
Thanks very much!
-Message d'origine-
De : Shawn
On 2/22/2018 9:50 AM, Hodder, Rick wrote:
I am migrating from SOLR 4.10.2 to SOLR 7.1.
All seems to be going well, except for one thing: the score that is coming back
for the resulting documents is giving different scores.
The absolute score has no meaning when you change something -- the
in
Cool, Thanks, Shawn. I was also looking the swapiness and it is set to
60. Will try this out and let you know. Thanks, again.
On Thu, Feb 22, 2018 at 10:55 AM, Shawn Heisey wrote:
> On 2/21/2018 7:58 PM, Susheel Kumar wrote:
>
>> Below output for prod machine based on the steps you described.
I am migrating from SOLR 4.10.2 to SOLR 7.1.
All seems to be going well, except for one thing: the score that is coming back
for the resulting documents is giving different scores.
The core uses a schema. Here's the schema info for the field that i am
searching on:
When searching maxrows=75
On 2/22/2018 8:53 AM, LOPEZ-CORTES Mariano-ext wrote:
With a 3 nodes cluster each 12GB and a corpus of 5GB (CSV format).
Is it better to disable completely Solr cache ? There is enough RAM for the
entire index.
The size of the input data will have an effect on how big the index is,
but it is
Thanks Antelmo, I'm trying to reproduce this now.
-Yonik
On Mon, Feb 19, 2018 at 10:13 AM, Antelmo Aguilar wrote:
> Hi all,
>
> I was wondering if the information I sent is sufficient to look into the
> issue. Let me know if you need anything else from me please.
>
> Thanks,
> Antelmo
>
> On Th
On 2/21/2018 7:58 PM, Susheel Kumar wrote:
Below output for prod machine based on the steps you described. Please
take a look. The solr searches are returning fine and no issue with
performance but since last 4 months swap space started going up. After
restart, it comes down to zero and then fe
Hello
With a 3 nodes cluster each 12GB and a corpus of 5GB (CSV format).
Is it better to disable completely Solr cache ? There is enough RAM for the
entire index.
Is there a way for reduce random queries under 1 second?
Thanks!
Hi,
The use case for this is that our indexing node has more shards than it has CPU
cores it is enough for indexing, but not enough to serve the search queries if
those queries are heavy. To put it out of serving requests we are using
in-house solution that routes the queries to pull replicas b
Hi,
We recently setup a 7.2.1 cloud with the intent to have the documents be
automatically deleted from the collection using the
DocExpirationUpdateProcessorFactory. We also have the cloud secured using
the BasicAuthenticationPlugin. Our current config settings are below.
The deployment is 3 node
Thanks for your answer, Mikhail.
Florian
-Ursprüngliche Nachricht-
Von: Mikhail Khludnev [mailto:m...@apache.org]
Gesendet: Dienstag, 6. Februar 2018 11:44
An: solr-user
Betreff: Re: Sort by nested field but only in matching nested documents
Hello Florian,
No. As an alternative you ca
All in all the index is about 250GB and it’s sharded in two dedicated VMs with
24GB of memory and it’s performing ok so far (queries take about 7 seconds, the
worst cases about 10). At some point in the past we needed to transition to
SolrCloud because a single Solr core, of course, wouldn’t sca
Right now we’re sharding the collection as we hit performance issues in the
past with legacy Solr (i.e. a single Solr core), and also we’re experimenting a
bit to see which replication factor we can get away with (in terms of resources
and cost). Unfortunately, PSQL isn’t yet an option due to th
22 matches
Mail list logo