[
https://issues.apache.org/jira/browse/SOLR-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233431#comment-13233431
]
Mark Miller commented on SOLR-3220:
-----------------------------------
Sorry - missed these issues going by - been busy with other things for a bit.
Yeah, I've seen this before. It happens when an error is returned rather than a
java bin response. I've seen it with 404's, sure it happens with other errors
at the container level. The '60' is the start of the html (if I remember right)
error response.
It makes debugging a bitch sometimes.
So for instance, for the ping handler, perhaps it wasn't found, or it errored.
For this, it could be an issue during startup or shutdown when a 404 can be
returned.
We should make a new issue for the problem - offhand I don't have a solution
though. Adding structure error support to Solr might help.
For this issue I first need to see if that exception even relates to the
failure - there is a good chance it does not. A server is stopped and started
in this test, and a query or update at the wrong time can return a 404 or some
other non success code. So you are likely to see this exception even if the
test passes.
> RecoveryZkTest test failure
> ---------------------------
>
> Key: SOLR-3220
> URL: https://issues.apache.org/jira/browse/SOLR-3220
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Attachments: TEST-org.apache.solr.cloud.RecoveryZkTest.xml
>
>
> observed a failure in RecoveryZkTest.testDistribSearch using r1298661 that
> had some odd looking (to me) log info.
> could not reproduce with identical seed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
