Hopefully this question makes sense.
At the moment I'm using a DisMax query which looks something like the
following (massively cut-down):
?defType=dismax
q=some query
qf=field_one^0.5 field_two^1.0
I've got some localisation work coming up where I'd like to use the value
of one, sparsely
since you don't have a static index
Erick
On Tue, Sep 24, 2013 at 4:13 AM, Neil Prosser neil.pros...@gmail.com
wrote:
Shawn: unfortunately the current problems are with facet.method=enum!
Erick: We already round our date queries so they're the same for at least
an hour so thankfully
.
This is definitely unusual...
Best,
Erick
On Thu, Sep 19, 2013 at 8:20 AM, Neil Prosser neil.pros...@gmail.com
wrote:
Apologies for the giant email. Hopefully it makes sense.
We've been trying out SolrCloud to solve some scalability issues with our
current setup and have run into problems
had lots of memory and zk related issues. What's the warmup time for
your caches? Have you tried disabling the caches?
Is this is static index or you documents are added continuously?
The answers to these questions might help us pin point the issue...
On Thursday, September 19, 2013, Neil
Apologies for the giant email. Hopefully it makes sense.
We've been trying out SolrCloud to solve some scalability issues with our
current setup and have run into problems. I'd like to describe our current
setup, our queries and the sort of load we see and am hoping someone might
be able to spot
as that seems.
or by using G1 :)
See http://blog.sematext.com/2013/06/24/g1-cms-java-garbage-collector/
Otis
--
Solr ElasticSearch Support -- http://sematext.com/
Performance Monitoring -- http://sematext.com/spm
On Mon, Jul 22, 2013 at 5:05 PM, Neil Prosser neil.pros...@gmail.com
running 4.3.1. I've since upgraded to 4.4.0.
If you need any more information or want me to do any filtering let me know.
On 24 July 2013 15:50, Timothy Potter thelabd...@gmail.com wrote:
Log messages?
On Wed, Jul 24, 2013 at 1:37 AM, Neil Prosser neil.pros...@gmail.com
wrote:
Great. Thanks
index into the Linux OS cache. Hopefully the 5GB minimum for field
cache and 8GB heap is what's causing this trouble right now.
On 24 July 2013 19:06, Shawn Heisey s...@elyograg.org wrote:
On 7/24/2013 10:33 AM, Neil Prosser wrote:
The log for server09 starts with it throwing
for
the new node to come back up. At the very least the new node you were
bringing back online will need to do a full index replication (old
style) to get caught up.
Best
Erick
On Fri, Jul 19, 2013 at 4:02 AM, Neil Prosser neil.pros...@gmail.com
wrote:
While indexing some documents
good results by upping the ZooKeeper timeout limit. So I guess
my first question is whether the nodes are actually going out of service
or whether it's just a timeout issue
Good luck!
Erick
On Mon, Jul 22, 2013 at 3:29 AM, Neil Prosser neil.pros...@gmail.com
wrote:
Very true. I
Sorry, I should also mention that these leader nodes which are marked as
down can actually still be queried locally with distrib=false with no
problems. Is it possible that they've somehow got themselves out-of-sync?
On 22 July 2013 13:37, Neil Prosser neil.pros...@gmail.com wrote:
No need
taken because I'm working with our cluster!
On 22 July 2013 19:26, Lance Norskog goks...@gmail.com wrote:
Are you feeding Graphite from Solr? If so, how?
On 07/19/2013 01:02 AM, Neil Prosser wrote:
That was overnight so I was unable to track exactly what happened (I'm
going off our Graphite
While indexing some documents to a SolrCloud cluster (10 machines, 5 shards
and 2 replicas, so one replica on each machine) one of the replicas stopped
receiving documents, while the other replica of the shard continued to grow.
That was overnight so I was unable to track exactly what happened
13 matches
Mail list logo
