[
https://issues.apache.org/jira/browse/SOLR-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692329#comment-16692329
]
Jason Gerlowski commented on SOLR-6595:
---------------------------------------
Wanted to check in on this and see which of the original concerns are still
issues:
bq. Status=0 when the cmd did not succeed
Still a problem, though it will soon be fixed for CREATE, the reporter's
original example here.
bq. The error printed does not tell which action failed
Still a problem, but a hard one: it's tough to guess which bits in the
exception chain are the helpful bits. The top and root of the chain are the
most likely entries to be interesting, but not always. Any truncation of the
exception chain is going to reduce the chance we're conveying the important
part.
bq. State of collection is not clean since it exists as far as ZK is concerned
but cores not created
This _should_ have already been fixed in SOLR-8983.
So I'd argue that fixing the {{status}} property should be our main goal. To
that end, I've attached a patch fixing this problem for CREATE on SOLR-5970. I
don't like the narrowness of that fix though will spend some time seeing if
there's a way it can be generalized at a different level of our collection API
processing. Going to assign this to myself.
> Improve error response in case distributed collection cmd fails
> ---------------------------------------------------------------
>
> Key: SOLR-6595
> URL: https://issues.apache.org/jira/browse/SOLR-6595
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.10
> Environment: SolrCloud with Client SSL
> Reporter: Sindre Fiskaa
> Priority: Minor
>
> Followed the description
> https://cwiki.apache.org/confluence/display/solr/Enabling+SSL and generated a
> self signed key pair. Configured a few solr-nodes and used the collection api
> to crate a new collection. -I get error message when specify the nodes with
> the createNodeSet param. When I don't use createNodeSet param the collection
> gets created without error on random nodes. Could this be a bug related to
> the createNodeSet param?- *Update: It failed due to what turned out to be
> invalid client certificate on the overseer, and returned the following
> response:*
> {code:xml}
> <response>
> <lst name="responseHeader"><int name="status">0</int><int
> name="QTime">185</int></lst>
> <lst name="failure">
> <str>org.apache.solr.client.solrj.SolrServerException:IOException occured
> when talking to server at: https://vt-searchln04:443/solr</str>
> </lst>
> </response>
> {code}
> *Update: Three problems:*
> # Status=0 when the cmd did not succeed (only ZK was updated, but cores not
> created due to failing to connect to shard nodes to talk to core admin API).
> # The error printed does not tell which action failed. Would be helpful to
> either get the msg from the original exception or at least some message
> saying "Failed to create core, see log on Overseer <node.name>
> # State of collection is not clean since it exists as far as ZK is concerned
> but cores not created. Thus retrying the CREATECOLLECTION cmd would fail.
> Should Overseer detect error in distributed cmds and rollback changes already
> made in ZK?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
