Hi,
How did you delete replica? Did you see any errors in logs after deleting? How
did/does it look from ZK perspective after deleting that replica?
Thanks,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/
Hi,
I've noticed that in SOLR-7484 Solr part of http request was moved to
SolrHttpCall. So there is no way to handle
SolrQueryRequest and SolrQueryResponse in SolrDispatchFilter.
Internal requet logging is SolrCore.execute(SolrRequestHandler,
SolrQueryRequest, SolrQueryResponse)
Is there is
Hi Erik,
Sorry for the late reply, I wasn't in my office this week...
So, I give more information:
* IC is a multi-value field defined like this:
* The request I use (i.e):
http://my_host/solr/collection/select?
q=ic:(A63C10* OR G06F22/086)
&start=0
&rows=10
&wt=json
&indent=true
&sort=pd+desc
Thanks a lot for your effort, Tim.
Looking at it from the Solr side, I see some use of local classes. The
snippet below in particular caught my eye (in
solr/core/src/java/org/apache/solr/search/ComplexPhraseQParserPlugin.java).
The instance of ComplexPhraseQueryParser is not the clean one from Luc
On Thu, 2017-10-05 at 21:56 -0700, S G wrote:
> So for large indexes, there is a chance that filterCache of 128 can
> cause bad GC.
Large indexes measured in document count, yes. Or you could argue that
a large index is likely to be served with a much larger heap and that
it will offset the increa
Hi
I need get faceted results by a date field. The facets must be two:
1) all values lower than the system date
2) and values greater than the system date,
¿it is possible get these two facet?
I'm reading wiki solr about facet.date and facet.range but I not get a
good solution.
Any idea
On Fri, 2017-10-06 at 13:16 +0200, Miguel Valencia Zurera wrote:
> I need get faceted results by a date field. The facets must be
> two:
> 1) all values lower than the system date
> 2) and values greater than the system date,
https://lucene.apache.org/solr/guide/6_6/working-with-dates.html#W
Hi,
I'm new to solr, and I use solr 6.6.
I have set it up and do some testing, I've noticed that fieldValueCache is
not used for multivalued field faceting (and any other query) at all, of
course I specified it previously in solrconfig.xml and set docVals for all
faceting fields to false in orde
On Fri, Oct 6, 2017 at 6:50 AM, Toke Eskildsen wrote:
> Letting the default use maxSizeMB would be better IMO. But I assume
> that FastLRUCache is used for a reason, so that would have to be
> extended to support that parameter first.
FastLRUCache is the default on the filter cache because it was
Thanks Chris,
That very likely is the reason. I had noticed the seed and realized that it
will be controlling the random input generation for the tests to make
failures reproducible. However, i didn't consider that it can also cause
test skipping.
Thanks!
Nawab
On Thu, Oct 5, 2017 at 3:13 PM, C
Hi,
I'm new to solr, and I'm using solr 6.6.
I did some testing with solr 4.9 and 6.6 on the same index with the same
faceting queries on the multivalued fields.
In first run (with empty cache) solr 6.6 performs much better, but when I
run same queries couple more times solr 4.9 is a little bit
If you're using regular faceting (as opposed to the JSON Facet API),
you can try facet.method=uif
https://issues.apache.org/jira/browse/SOLR-8466
Background:
UIF (UnInvertedField which are the entries in the FieldValueCache) was
completely removed from use at some point in the 5.x timeframe.
It wa
Thanks for the clarification. I'll change my code to accommodate this
behavior.
On Thu, Oct 5, 2017 at 6:24 PM, Chris Hostetter
wrote:
> : > "startTime":"2013-02-10T18:36:07.000Z"
> ...
> : handler. It gets added successfully but when I retrieve this document
> back
> : using "id
Hi Yonik,
Thanks for your answer :).
It works.
Another question:
What is recommended to be used in solr 6.6 for faceting (docValues or
UnInvertedField), because UnInvertedField performs better for subsequent
requests?
I assume that docValues is more beneficial in terms of heap memory use, bu
On Fri, Oct 6, 2017 at 12:45 PM, sile wrote:
> Hi Yonik,
>
> Thanks for your answer :).
>
> It works.
>
> Another question:
>
> What is recommended to be used in solr 6.6 for faceting (docValues or
> UnInvertedField), because UnInvertedField performs better for subsequent
> requests?
>
> I assume
: I would guess that your first query is hitting the queryResultCache.
yeah, that's almost certainly why you're seeing the "page#0" query be so
fast -- but IIRC the cursorMark pages can't be cached in the same way?
where you'll start to see significant speed ups is in in the subsequent
"page
: https://lucene.apache.org/solr/guide/6_6/working-with-dates.html#Workin
: gwithDates-DateMath
:
: Your query would be something like
: mydate:[* TO NOW/DAY] AND mydate:[NOW+1DAY/DAY TO *]
specifically you could use those with "facet.query" ... instead of trying
to do them with "facet.range"
The replica was deleted using the deleteReplica collections API call. The
call timed out, but eventually completed. However something still held a
write lock, and it was still held a day later, but the replica was removed
as far as we could tell in the solr admin console.
Since it was a developmen
Diego, I wrote this article today after our initial high-level review at
OpenSource Connections
http://opensourceconnections.com/blog/2017/10/06/vespa-vs-lucene-initial-impressions/
On Wed, Sep 27, 2017 at 11:44 AM Diego Ceccarelli (BLOOMBERG/ LONDON) <
dceccarel...@bloomberg.net> wrote:
> Hi al
for future reference, a less harsh way to fix it would be to
> stop the Solr instance where the replica resides
> rm -rf SOLR_HOME/collection1_replia1_shard1
where "collection1_replica1_shard1" is the directory of the replica in
question, you should see a "core.properties" file in that directory..
Unfortunately as developers we have no access to the actual solr nodes, and
certainly no privileges to delete stuff, even in the development
environment.
On Fri, Oct 6, 2017 at 1:34 PM, Erick Erickson
wrote:
> for future reference, a less harsh way to fix it would be to
> > stop the Solr instanc
That could be it. I'm not able to reproduce this with trunk. More next week.
In trunk, if I add this to schema15.xml:
This test passes.
@Test
public void testCharFilter() {
assertU(adoc("iso-latin1", "cr\u00E6zy tr\u00E6n", "id", "1"));
assertU(comm
We are using Solr 6.2.0 in solrcloud mode
I have a QA solrcloud that has multiple collections. All collections have 2
shards each with two replicas.
I have several replicas where the numDocs in the same shard do not match.
In two collections with three different shards I have one replica with dat
Shouldn't be happening of course (replicas with different numbers of
docs), at least permanently. It can regularly happen on a _temporary_
basis however. And there are ways you can cause this to happen
permanently. Here's an outline.
> temporarily out of sync. Due to the fact that commits happen a
When 'polt' is passed as keyword, both suggestions and collations
parameters are returned. But if I pass 'tag:polt' as search query then only
suggestions parameter is returned. Is this a bug?
6 October 2017, Apache Solr™ 7.0.1 available
Solr is the popular, blazing fast, open source NoSQL search platform from the
Apache Lucene project. Its major features include powerful full-text search,
hit highlighting, faceted search and analytics, rich document parsing,
geospatial search, exte
This solrcloud has had some issues of late. We had a network glitch which
caused a shard leader of one of the collections write over 5000 0 length
tlogs to its filesystem. Whenever it started up it ran out of file handles
which killed the IndexWriter and caused lots of unhappy collections. This
may
27 matches
Mail list logo