We printed in most of the places but could not get any significant
differences between successful and error documents. We modified our logic
to use direct http client and posted the JSON messages directly to solr
cloud. Most of the ids are fine now.
But we still see same issue with minimal doc
You may want to dig deeper to see what's going on. It shouldn't be the
case. Most likely your code is producing the SolrInputDocument in a
different way which is making it fail. You can write SolrInputDocument or
print it in json to compare...
On Fri, Jul 21, 2017 at 1:31 AM, mesenthil1 <
senthi
While debugging following are the findings.
When we send the same document as json, it is getting indexed without an
issue. When the same document is converted as SolrInputDocument and sent to
solr using SolrServer, it fails.
--
View this message in context:
http://lucene.472066.n3.nabble.com
You can try to submit only the failed documents directly one by one/all and
see if you get any error etc.
On Thu, Jul 20, 2017 at 11:01 AM, Walter Underwood
wrote:
> If Apache is returning 400, then it really is a bad request. Debug the
> request and fix it.
>
> wunder
> Walter Underwood
> wun..
If Apache is returning 400, then it really is a bad request. Debug the request
and fix it.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jul 19, 2017, at 11:27 PM, mesenthil1
> wrote:
>
> Hi,
> This is happening repeatedly for few documents.
Hi,
This is happening repeatedly for few documents. When we compared with other
similar documents, we could not find any difference.
As we are seeing 400 on apache, the request is not submitted to solr. So
unable to find out the cause.
Senthil
--
View this message in context:
http://luce
A 400 would not be a failure to connect. A 400 means that the client is sending
a bad request.
Look at the Solr logs. Most likely, the document is invalid.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jul 19, 2017, at 7:54 AM, Susheel Kumar wro
Is that always the problem with those documents or is it random. If it is
the same documents always, look what is different in those docs.
Usually i have seen these errors once in a while when SolrJ unable to
connect/communicate with Solr.
On Wed, Jul 19, 2017 at 10:23 AM, subbarao
wrote:
> Hi
