I use the solr is 6.0 version, the solrj is 6.0 version, using
SolrCloud mode deployment, in my code did not make an explicit commit,
configure the autoCommit and softAutoCommit, using the
ConcurrentUpdateSolrClient class.
When we send 100 million data, often read timeout exception occurred
in
So what are people recommending for SOLR on AWS on Amazon AMI - ext4 or xfs?
I saw an article about MongoDB - saying performance on Amazon was better
due to a mutex issue on ext4 files and threaded calls.
I have been using ext4 for a long time, but I am moving to r3.* instances
and TRIM /
Thanks. I'll look into that stuff. The counts issue is really not a serious
problem for us far as I know.
On Wed, Dec 21, 2016 at 9:08 PM, Erick Erickson
wrote:
> "grab the response" is a bit ambiguous here in Solr terms. Sure,
> a SearchComponent (you can write a
Awesome explanation Eric, I'll be filing this away for future reference.
On Dec 21, 2016 7:08 PM, "Erick Erickson" wrote:
"grab the response" is a bit ambiguous here in Solr terms. Sure,
a SearchComponent (you can write a plugin) gets the response,
but it only sees the
"grab the response" is a bit ambiguous here in Solr terms. Sure,
a SearchComponent (you can write a plugin) gets the response,
but it only sees the final list being returned to the user, i.e. if you
have rows=15 it sees only 15 docs. Not sure that's adequate,
in the case above you could easily not
It would be custom code and I have something along those lines, although it
throws an error instead of changing the response...
Rushing now and can't go into more detail right now.
On Dec 21, 2016 6:57 PM, "Mike Thomsen" wrote:
> We're trying out some ideas on locking
We're trying out some ideas on locking down solr and would like to know if
there is a public API that allows you to grab the response before it is
sent and inspect it. What we're trying to do is something for which a
filter query is not a good option to really get where we want to be.
Basically,
There is not nearly enough information here to say
anything helpful. Please attach the stack trace,
the query used etc. IOW, whatever you think would
help someone else reproduce the problem.
What version of Solr are you using?
Best,
Erick
On Wed, Dec 21, 2016 at 11:14 AM, nelias
Hello ,
I am running a simple search expression on a secured solr server running on
cloud mode . Ran the stream exception in admin console . Getting
java.util.concurrent.ExecutionException . Ran the same via SolrJ and got
inside the source code and it's saying Divide by zero exception is coming
Hi All,
I've a field like that:
When I run a suggester on my_field_1 it returns response. However
my_field_2 doesn't. I've defined suggester as:
suggester
FuzzyLookupFactory
DocumentDictionaryFactory
What can be the reason?
Kind Regards,
Furkan KAMACI
Also curious why such a large heap is required... If it's due to field
caches being loaded I'd highly recommend MMapDirectory (if not using
already) and turning on DocValues for all fields you plan to perform
sort/facet/analytics on.
steve
On Wed, Dec 21, 2016 at 9:25 AM Pushkar Raste
You should probably have as small a swap as possible. I still feel long GCs
are either due to swapping or thread contention.
Did you try to remove all other G1GC tuning parameters except for the
ParallelRefProcEnabled?
On Dec 19, 2016 1:39 AM, "forest_soup" wrote:
>
Yeah, that makes sense indeed.
Thanks!
Markus
-Original message-
> From:Chris Hostetter
> Sent: Thursday 15th December 2016 19:44
> To: solr-user@lucene.apache.org
> Subject: RE: DocTransformer not always working
>
>
> : Well, i can work with this really
13 matches
Mail list logo