Hi Eric,
What are you recommendations for SolrCloud DR strategy.
Thanks,
Raji
On Sun, Mar 29, 2020 at 6:25 PM Erick Erickson
wrote:
> I don’t recommend CDCR at this point, I think there better approaches.
>
> The root problem is that CDCR uses tlog files as a queueing mechanism.
> If the conne
Thanks Eric. I don't seeing anywhere that CDCR is not recommended for
production use. Took the thread dump. Seeing about 140 CDCR threads
cdcr-replicator-219-thread-8" #787 prio=5 os_prio=0 tid=0x7f7c34009000
nid=0x50a waiting on condition [0x7f7ec871b000]
java.lang.Thread.State: WAIT
> Case 3 let;s extend it with expand=true:
> { "responseHeader":{ "status":0, "QTime":1, "params":{
> "q":"author:\"William
> Shakespeare\"", "fq":"{!collapse field=title}&expand=true", "_":
> "1585603593269"}},
>
I think it is because, expand=true parameter is not passed properly. As you
can see f
Oh dear. Your autowarming is almost, but not quite totally, useless given
your 2 second soft commit interval. See:
https://lucidworks.com/post/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
So autowarming is probably not a cure, when you originally said “commit” I was
assumin
figured out referred to the docs here
https://github.com/apache/lucene-solr/commit/0ce635ec01e9d3ce04a5fbf5d472ea9d5d28bfee?short_path=421a323#diff-421a323f596319f0485e0b03070d94e6
Thanks
Jay
On Mon, Mar 30, 2020 at 3:38 PM Jay Potharaju wrote:
> Hi,
> I am trying to update the connection &
Thanks, Erick,
The process time execution based on debugQuery between the query and facets
is as follows
query 10ms
facets 4900ms
since max time is spent on facet processing (docValues enabled), query and
filter cache do no apply to this, correct?
- Autowarm count is at 32 for both and aut
Hi,
I am trying to update the connection & sockettime out value for my `select`
handler. After updating the configs i do not see that value being set and
it defaults to 60 sec.
How can i update these values?
Also looks like the docs have sockeTimeout & connectionTimeout values
swapped.
https://gi
Hi Munendra,
Let's see the 3 scenario:
1. Query without collapse
2. Query with collapse
3. Query with collapse and expand
I made a mini book database for this:
Case 1:
{ "responseHeader":{ "status":0, "QTime":0, "params":{ "q":"author:\"William
Shakespeare\"", "_":"1585603593269"}}, "response":{"nu
Correcting some typos ...
Thanks, Eric.
1) We are using dynamic string field for faceting where indexing =false and
stored=false . By default docValues are enabled for primitive fields (solr
6.6.), so not explicitly defined in schema. Do you think its wrong
assumption? Also I do not see this fiel
OK, sounds like docValues is set.
Sure, in solrconfig.xml, there are two sections “firstSearcher” and
“newSearcher”.
These are queries (or lists of queries) that are fired as part of autowarming
when Solr is first started (firstSearcher) or when a commit happens that opens
a new searcher (newSear
Thanks, Eric.
1) We are using dynamic string field for faceting where indexing =false and
stored=false . By default docValues are enabled for primitive fields (solr
6.6.), so not explicitly defined in schema. Do you think its wrong
assumption? Also I do not this field listed in feild cache, but do
Response spikes after commits are almost always something to do
with autowarming or docValues being set to false. So here’s what
I’d look at, in order.
1> are the fields used defined with docValues=true? They should be.
With this much variance it sounds like you don’t have that value set.
You’ll h
Hi SOLR Community,
I've been looking at performance tuning solr's GC lately. I found this
helpful article on the matter.
https://cwiki.apache.org/confluence/display/SOLR/ShawnHeisey
One thing the article does not address is the GC1's ability to use string
deduplication:
https://blog.gceasy.io/201
I wanted to ask *yet again* whether anyone could please clarify what this error
means?
The wording could be interpreted as a benign "I found that there was nothing
which needed to be done after all"; but were that to be the meaning of this
error, why would it be flagged as an ERROR rather than
A facet heavy query which uses docValue fields for faceting returns about
5k results executes between 10ms to 5 secs and the 5 secs time seems to
coincide with after a hard commit.
Does that have any relation? Why the fluctuation in execution time?
Thanks,
Revas
Please share the complete request. Also, does number of results change with
& without collapse. Usually title would be unique every document. If that
is the case then, there won't be anything to expand right?
On Mon, Mar 30, 2020, 8:22 PM Szűcs Roland
wrote:
> Hi Munendra,
> I do not get error
Hi Munendra,
I do not get error . The strange thing is that I get exactly the same
response with fq={!collapse field=title} versus fq={!collapse
field=title}&expand=true.
Collapse works properly as a standalone fq but expand has no impact. How
can I have access to the "hidden" documents then?
Rol
Hey,
Could you please share the stacktrace or error message you received?
On Mon, Mar 30, 2020, 7:58 PM Szűcs Roland
wrote:
> Hi All,
>
> I manage to use edismax queryparser in solr 8.4.1 with collapse without any
> problem. I tested it with the SOLR admin GUI. So fq={!collapse field=title}
> wo
Hi All,
I manage to use edismax queryparser in solr 8.4.1 with collapse without any
problem. I tested it with the SOLR admin GUI. So fq={!collapse field=title}
worked fine.
As soon as I use the example from the documentation and use: fq={!collapse
field=title}&expand=true, I did not get back any
19 matches
Mail list logo
