[
https://issues.apache.org/jira/browse/SOLR-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013351#comment-14013351
]
Shalin Shekhar Mangar commented on SOLR-6117:
---------------------------------------------
bq. The actual error stack trace gets printed in the logs. Should we change how
the remaining also get handled?
I think an exception should be returned in the response if possible. The old
days of just logging exceptions are gone. We can't expect users to sift through
GBs of logs in SolrCloud to find the reason behind the failure. But that's a
big change so I think we should do it in another issue.
> Replication command=fetchindex always return success.
> -----------------------------------------------------
>
> Key: SOLR-6117
> URL: https://issues.apache.org/jira/browse/SOLR-6117
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 4.6
> Reporter: Raintung Li
> Assignee: Shalin Shekhar Mangar
> Attachments: SOLR-6117.patch, SOLR-6117.patch, SOLR-6117.txt
>
>
> Replication API command=fetchindex do fetch the index. while occur the error,
> still give success response.
> API should return the right status, especially WAIT parameter is
> true.(synchronous).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
