[
https://issues.apache.org/jira/browse/KNOX-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066719#comment-18066719
]
ASF subversion and git services commented on KNOX-3282:
-------------------------------------------------------
Commit da88e2445090f1c6c527f6f96173fa82650c4738 in knox's branch
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=da88e2445 ]
KNOX-3282: Add certain CM service discovery error stack traces in the log at
INFO level (#1179)
> CM discovery error stacktrace to be printed at INFO level
> ---------------------------------------------------------
>
> Key: KNOX-3282
> URL: https://issues.apache.org/jira/browse/KNOX-3282
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 2.1.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When a service discovery error occurs, the following log entry is added in
> gateway.log with the default log4j settings:
> {noformat}
> ERROR discovery.cm (ClouderaManagerServiceDiscovery.java:discover(233)) -
> Encountered an error during cluster (MCDH5S) discovery:
> com.cloudera.api.swagger.client.ApiException: Not Found{noformat}
> This is just a sample, there can be a variety of reasons why Knox couldn't
> connect to CM for discovery.
> While troubleshooting such issues, it's hard to determine the root cause
> without setting the log level to {{DEBUG}} (at least for
> {{{}org.apache.knox.gateway.topology.discovery.cm{}}}).
> Suggested change: let stack trace be printed out in the logs even on {{INFO}}
> level in this case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
