I'm reworking the test case, so hold off on doing that. If you want to
raise a JIRA, though. please do and attach your patch...
On Thu, Dec 20, 2018 at 10:53 AM Erick Erickson wrote:
>
> Nothing that I know of was _intentionally_ changed with this between
> 6x and 7x. That said, nothing that I kn
Hi Peter,
Use of an RPT field for distance sorting/boosting is to be avoided where
possible because it's very inefficient at this specific use-case. Simply
use LatLonType for this task, and continue to use RPT for the filter/search
use-case.
Also I see you putting a space between the coordinates
Thank you Erick.
I will also try ZooKeeper 3.4.13 with Solr 7.6.
Thanks,
Yasufumi.
2018年12月20日(木) 9:58 Erick Erickson :
> As far as anyone knows, the issues in SOLR-12727 are test-only issues.
> That said, I don't know of anyone using ZooKeeper 3.4.13 in the field.
> That said I also haven't he
We are experiencing almost nightly solr crashes due to Japanese queries. I’ve
been able to determine that one of our field types seems to be a culprit. When
I run a much reduced version of the query against out DEV solrcloud I see the
memory usage jump from less than a gb to 5gb using only a sin
Nothing that I know of was _intentionally_ changed with this between
6x and 7x. That said, nothing that I know of was done to verify that
TLOG and PULL replicas (added in 7x) were handled correctly. There's a
test "TestRebalanceLeaders" for this functionality that has run since
the feature was put
Kyle - Thanks so much for the followup on this. Rarely do we get to
see results compared with detail.
Can you share the Solr HDFS configuration settings that you tested
with? Blockcache and direct memory size? I'd be curious just as a
reference point.
Kevin Risden
On Thu, Dec 20, 2018 at 10:31 A
The Lucene PMC is pleased to announced that the Solr Reference Guide for
7.6 is now available.
This 1,415 page PDF is the definitive guide to Apache Solr, the search
server built on Apache Lucene.
The PDF can be downloaded from:
https://www.apache.org/dyn/closer.cgi/lucene/solr/ref-guide/apache-s
Hi Vadim,
I just tried it with 6.6.5.
In my test cloud with 5 shards, 5 nodes, 3 cores per node it missed
one shard to become leader. But noticed that one shard already was
leader. No errors or exceptions in logs.
May be I should enable debug logging and try again to see all logging
messages from
You can go here: https://issues.apache.org/jira, create a signon and
freely create JIRAs. Please attach the patch as well. I hadn't really
thought very carefully about REBALANCELEADERS and the new replica
types, but that does change the use-case.
Best,
Erick
On Thu, Dec 20, 2018 at 3:31 AM Vadim
One has an "AND" and one has an "OR"?
You obviously have some kind of issue or anomaly, but you haven't told
us what behavior _is_, so we have no idea how to answer.
try running your query through with &debug=query. Also be aware that
by default queries do NOT implement boolean logic, see:
https
Hi All,
To close this off, I'm sad to report that we've come to a end with Solr on
HDFS.
Here's what we finally did:
- created two brand-new identical Solr cloud clusters, one on HDFS and one
on local disk.
- 1 replica per node. Each node 16GB ram.
- Added documents.
- Compared start-up times
Yes! It works!
I have tested RebalanceLeaders today with the patch provided by Endika Posadas.
(http://lucene.472066.n3.nabble.com/Rebalance-Leaders-Leader-node-deleted-when-rebalancing-leaders-td4417040.html)
And at last it works as expected on my collection with 5 nodes and about 400
shards.
Or
12 matches
Mail list logo
