[
https://issues.apache.org/jira/browse/SOLR-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602005#comment-14602005
]
Gregory Chanan commented on SOLR-7637:
--------------------------------------
bq. From debugging perspective we are mostly insterested in ZOOKEEPER exception
- which is represented by the first cause.
It is today -- there's no guarantee that it will be in the future. I realize
the first exception today is pretty useless. What about getting the root
cause, e.g.
http://commons.apache.org/proper/commons-lang/javadocs/api-3.1/org/apache/commons/lang3/exception/ExceptionUtils.html#getRootCause(java.lang.Throwable)
? Or providing an example where that is not the correct thing to do.
bq. At least in Cloudera Manager environment, using System.err simplifies
debugging since all the script executions are logged in stderr.log file. If we
use System.out, the error message will go to stdout.log file instead (which can
be confusing for the user). May be add it to both?
I think this is a reasonable argument, but seems most appropriate for a
different jira. If you are motivated, feel free to open another jira to
discussing moving the errors from System.out to System.err.
> Improve error logging in the zkcli CLUSTERPROP command
> ------------------------------------------------------
>
> Key: SOLR-7637
> URL: https://issues.apache.org/jira/browse/SOLR-7637
> Project: Solr
> Issue Type: Improvement
> Reporter: Hrishikesh Gadre
> Assignee: Gregory Chanan
> Priority: Trivial
> Attachments: SOLR-7637.patch
>
>
> SOLR-7176 introduced capability to update Solr cluster properties via ZK CLI.
> The error logging implemented as part of that fix was not proper (i.e. the
> actual error was getting masked). We should improve the error logging to
> explicitly state the root cause.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
