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 <susheel2...@gmail.com> wrote: > > 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 <vuppalasubba...@gmail.com> > wrote: > >> Hi all, >> >> we have solr cloud setup with 2 shards. >> >> In this we trying to index documents by taking a json format input, and >> creating a SolrDocument. and pushing to solr through solrJ. >> >> Then it is throwing exception saying *"SolrUpdate got error: IOException >> occured when talking to server" * >> >> and in apache it is throwing 400 response code. But only few documents are >> having this problem.Some documents are indexing fine. >> >> Can anybody help us in this issue? >> >> >> Thanks, >> Subbarao. >> >> >> >> -- >> View this message in context: http://lucene.472066.n3. >> nabble.com/Getting-IO-Exception-while-Indexing-tp4346801.html >> Sent from the Solr - User mailing list archive at Nabble.com. >>
