Thanks for you inputs.
Regards,
Modassar
On Tue, Dec 30, 2014 at 8:41 PM, Jack Krupansky
wrote:
> I actually did that once as a test years ago, as well as support for
> "paging" through the wildcard terms with a starting offset, and it worked
> great.
>
> One way to think of the feature is as t
I actually did that once as a test years ago, as well as support for
"paging" through the wildcard terms with a starting offset, and it worked
great.
One way to think of the feature is as the ability to "sample" the values of
the wildcard. I mean, not all queries require absolute precision. Someti
On 12/30/2014 4:16 AM, Modassar Ather wrote:
> In the query having lots of wildcard can we put a limitation on number of
> expansion of terms done against a wildcard token something like
> maxBooleanClauses?
I'm not aware of anything for limiting wildcard terms, but I'm willing
to be surprised.
A
Hi,
In the query having lots of wildcard can we put a limitation on number of
expansion of terms done against a wildcard token something like
maxBooleanClauses?
Thanks,
Modassar
On Mon, Dec 29, 2014 at 11:15 AM, Modassar Ather
wrote:
> Thanks Jack for your suggestions.
>
> Regards,
> Modassar
Thanks Jack for your suggestions.
Regards,
Modassar
On Fri, Dec 26, 2014 at 6:04 PM, Jack Krupansky
wrote:
> Either you have too little RAM on each node or too much data on each node.
>
> You may need to shard the data much more heavily so that the total work on
> a single query is distributed
Either you have too little RAM on each node or too much data on each node.
You may need to shard the data much more heavily so that the total work on
a single query is distributed in parallel to more nodes, each node having a
much smaller amount of data to work on.
First, always make sure that th
Thanks for your suggestions Erick.
This may be one of those situations where you really have to
push back at the users and understand why they insist on these
kinds of queries. They must be very patient since it won't be
very performant. That said, I've seen this pattern; there are
certainly valid
There's no magic bullet here that I know of. If your requirements
are to support these huge, many-wildcard queries then you only
have a few choices:
1> redo the index. I was surprised at how little it bloated the
index as far as memory required is concerned to add ngrams.
The key here is that ther
Thanks for your response.
How many items in the collection ?
There are about 100 millions documents.
How are configured cache in solrconfig.xml ?
Each cache has size attribute as 128.
Can you provide a sample of the query ?
Does it fail immediately after solrcloud startup or after several hours
And you didn’t give how many RAM on each servers ?
2014-12-24 8:17 GMT+01:00 Dominique Bejean :
> Modassar,
>
> How many items in the collection ?
> I mean how many documents per collection ? 1 million, 10 millions, …?
>
> How are configured cache in solrconfig.xml ?
> What are the size attribute
Modassar,
How many items in the collection ?
I mean how many documents per collection ? 1 million, 10 millions, …?
How are configured cache in solrconfig.xml ?
What are the size attribute value for each cache ?
Can you provide a sample of the query ?
Does it fail immediately after solrcloud star
Thanks for your suggestions.
I will look into the link provided.
http://wiki.apache.org/solr/SolrPerformanceProblems#Java_Heap
This is usually an anti-pattern. The very first thing
I'd be doing is trying to not do this. See ngrams for infix
queries, or shingles or ReverseWildcardFilterFactory or.
Hi,
I agree Erick it could be a good think to have more details about your
configuration and collection.
Your heap size is 32Gb. How many RAM on each servers ?
By « 4 shard Solr cluster », you mean a 4 nodes Solr servers or a
collection with 4 shards ?
So, how many nodes in the cluster ?
How ma
Second most important part of your message:
"When executing a huge query with many wildcards inside it the server"
This is usually an anti-pattern. The very first thing
I'd be doing is trying to not do this. See ngrams for infix
queries, or shingles or ReverseWildcardFilterFactory or.
And if
On 12/23/2014 4:34 AM, Modassar Ather wrote:
> Hi,
>
> I have a setup of 4 shard Solr cluster with embedded zookeeper on one of
> them. The zkClient time out is set to 30 seconds, -Xms is 20g and -Xms is
> 24g.
> When executing a huge query with many wildcards inside it the server
> crashes and bec
To add to the details of above issue the query as soon it is executed, even
before the OutOfMemory error causes the solr servers to become
non-responsive.
On Tue, Dec 23, 2014 at 5:04 PM, Modassar Ather
wrote:
> Hi,
>
> I have a setup of 4 shard Solr cluster with embedded zookeeper on one of
> t
16 matches
Mail list logo
