[
https://issues.apache.org/jira/browse/SOLR-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14601977#comment-14601977
]
Hrishikesh Gadre commented on SOLR-7637:
----------------------------------------
>>Why is the first cause the important one to print? Seems arbitrary?
>From debugging perspective we are mostly insterested in ZOOKEEPER exception -
>which is represented by the first cause.
>>Why are the errors going to stderr when all the other errors in the script go
>>to stdout?
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?
> 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]
