The warning isn’t what’s affecting performance, it’s just an indication that
you’re committing too often. Technically you’re opening searchers too often.
Searchers are opened for several reasons;
1> your autocommit with openSearcher=true interval expires
2> your soft commit interval expires
3> yo
Hello,
We have Apache Solr version 6.2.1 installed on server and we are getting
this warning on Apache Solr log from few days which has affected
performance of solr queries and put latency on our App:
SolrCore [user_details] PERFORMANCE WARNING: Overlapping onDeckSearchers=2
So we have followed
Hi,Can someone respond on this please?Or, can you direct me to the right
contact who may know about these issues.Regards,RiteshFrom:
"Ritesh"<rved...@rediffmail.com>Sent: Tue, 19 Dec 2017
18:06:13To: <solr-user@lucene.apache.org>Subject: Re: recurring Solr
warning message
On 12/19/2017 5:36 AM, Ritesh wrote:
Hello,Can you help on the below issue please?My solr box keep on giving
warnings about every 30 seconds:
WARN null ServletHandler /solr/sitecore/select
org.apache.solr.common.SolrException: application/x-www-form-urlencoded
invalid: missing key
It looks li
on this?Regards,RiteshFrom:
GitHub Staff <supp...@github.com>Sent: Thu, 14 Dec 2017 00:05:54To:
Ritesh <rved...@rediffmail.com>Subject: Re: recurring Solr warni
I'm working on adding multi-language search to our application.
We are multi-language by field, that is all of the languages are in the
same collection. We have a lot of scientific data which often will have
English terms mixed in with Chinese (or other language). The requirement is
that for a lan
There is nothing else running on port that I am trying to use: 15101. 15102
works fine.
On Fri, Mar 3, 2017 at 2:25 PM Satya Marivada
wrote:
> Dave and All,
>
> The below exception is not happening anymore when I change the startup
> port to something else apart from that I had in original start
Dave and All,
The below exception is not happening anymore when I change the startup port
to something else apart from that I had in original startup. The original
starup, if I have started without ssl enabled and then startup on the same
port with ssl enabled, it is when this warning is happening
“Brittle” means that if the node fails, your cluster cannot change until the
node is back up. Single point of failure.
The whole point of Zookeeper is redundant protection against failure. So
running a single Zookeeper node is just wrong.
A Zookeeper ensemble needs to be an odd number of insta
It's a brittle ZK configuration. A typical ZK quorum is three nodes for
most production systems. One is fine, though, for development provided the
system it's on is not overloaded.
On Mon, Feb 27, 2017 at 6:43 PM, Rick Leir wrote:
> Hi Mike
> We are using a single ZK node, I think. What problems
Hi Mike
We are using a single ZK node, I think. What problems should we expect?
Thanks -- Rick
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
When you transition to an external zookeeper, you'll need at least 3 ZK
nodes. One is insufficient outside of a development environment. That's a
general requirement for any system that uses ZK.
On Sun, Feb 26, 2017 at 7:14 PM, Satya Marivada
wrote:
> May I ask about the port scanner running? Ca
Hi All,
I have configured solr with SSL and enabled http authentication. It is all
working fine on the solr admin page, indexing and querying process. One
bothering thing is that it is filling up logs every second saying no
authority, I have configured host name, port and authentication parameters
I don't know about your network setup but a port scanner sometimes can be an it
security device that, well, scans ports looking to see if they're open.
> On Feb 26, 2017, at 7:14 PM, Satya Marivada wrote:
>
> May I ask about the port scanner running? Can you please elaborate?
> Sure, will try
May I ask about the port scanner running? Can you please elaborate?
Sure, will try to move out to external zookeeper
On Sun, Feb 26, 2017 at 7:07 PM Dave wrote:
> You shouldn't use the embedded zookeeper with solr, it's just for
> development not anywhere near worthy of being out in production.
You shouldn't use the embedded zookeeper with solr, it's just for development
not anywhere near worthy of being out in production. Otherwise it looks like
you may have a port scanner running. In any case don't use the zk that comes
with solr
> On Feb 26, 2017, at 6:52 PM, Satya Marivada wrote
Hi All,
I have configured solr with SSL and enabled http authentication. It is all
working fine on the solr admin page, indexing and querying process. One
bothering thing is that it is filling up logs every second saying no
authority, I have configured host name, port and authentication parameters
17 matches
Mail list logo
