Your solr logs on the server should have more details than just
the bare error in the full stack trace. Those would help
figure out what's happening.
Best,
Erick
On Mon, Feb 4, 2019 at 3:14 PM Webster Homer
wrote:
>
> We have a number of collections in a Solrcloud.
>
> The cloud has 2 shards eac
We have a number of collections in a Solrcloud.
The cloud has 2 shards each with 2 replicas, 4 nodes. On one of the nodes I am
seeing a lot of errors in the log like this:
2019-02-04 20:27:11.831 ERROR (qtp1595212853-88527) [c:sial-catalog-product
s:shard1 r:core_node4 x:sial-catalog-product_sha
Hi,
If I request some query which is incorrect grammatically, error message is
shown in web browser but not in my python request code.
It just outputs "400 Bad Request".
How do I get error message in my python code?
Below is sample code...
-
On 3/7/2016 3:15 PM, Steven White wrote:
> In Solr's solr-8983-console.log I see the following (about 50 in a span of
> 24 hours when index is on going):
>
> WARNING: Couldn't flush user prefs:
> java.util.prefs.BackingStoreException: Couldn't get file lock.
This is not directly related to Sol
Re-posting. Anyone has any idea about this question? Thanks.
Steve
On Mon, Mar 7, 2016 at 5:15 PM, Steven White wrote:
> Hi folks,
>
> In Solr's solr-8983-console.log I see the following (about 50 in a span of
> 24 hours when index is on going):
>
> WARNING: Couldn't flush user prefs:
> j
Hi folks,
In Solr's solr-8983-console.log I see the following (about 50 in a span of
24 hours when index is on going):
WARNING: Couldn't flush user prefs:
java.util.prefs.BackingStoreException: Couldn't get file lock.
What does it mean? Should I wary about it?
What about this one:
118
Thanks Shawn,
I will create a JIRA. I just wasn't sure if there was another RC
afterwards and it could fit in there. Not very familiar with process
yet.
Regards,
Alex.
Personal blog: http://blog.outerthoughts.com/
LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch
- Time is the quality
On 4/24/2013 5:02 PM, Alexandre Rafalovitch wrote:
I am testing 4.3rc3. It looks ok, but I notice that some log messages
could be more informative. For example:
680 [coreLoadExecutor-3-thread-3] WARN
org.apache.solr.schema.IndexSchema – schema has no name!
Would be _very nice_ to know which cor
Hello,
I am testing 4.3rc3. It looks ok, but I notice that some log messages
could be more informative. For example:
680 [coreLoadExecutor-3-thread-3] WARN
org.apache.solr.schema.IndexSchema – schema has no name!
Would be _very nice_ to know which core this is complaining about.
Later, once the
On 5/10/2012 2:02 AM, Tolga wrote:
Apache servers are returning my post with the status messages
HTML_FONT_SIZE_HUGE,HTML_MESSAGE,HTTP_ESCAPED_HOST,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,URI_HEX,WEIRD_PORT.
I've tried clearing all formatting and a re-post, but the same thing
occurred.
Hi,
Apache servers are returning my post with the status messages
HTML_FONT_SIZE_HUGE,HTML_MESSAGE,HTTP_ESCAPED_HOST,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,URI_HEX,WEIRD_PORT.
I've tried clearing all formatting and a re-post, but the same thing
occurred. What to do?
Regards,
On Fri, Feb 22, 2008 at 7:38 AM, amamare <[EMAIL PROTECTED]> wrote:
> Hi,
> Solr apparently writes loads of error messages with every update, commit,
> search etc. Everything seems to be fine, searching and indexing is correct
> and fast, but we are concerned it might affect
Hi,
Solr apparently writes loads of error messages with every update, commit,
search etc. Everything seems to be fine, searching and indexing is correct
and fast, but we are concerned it might affect other parts of the system if
they are in fact symptoms of errors internal to Solr. It seems that
: Is there any parameter to set the max. number of error messages..
: The Solr system was killed after a couple of error messages which caused by
: WRONG QUERY
are you refering to maxing out the number of error messages in the log
file? There may be a JDK LoggingFilter that can ignore
Is there any parameter to set the max. number of error messages..
The Solr system was killed after a couple of error messages which caused by
WRONG QUERY
Thanks,
Jae
15 matches
Mail list logo