[
https://issues.apache.org/jira/browse/KNOX-3282?focusedWorklogId=1010204&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1010204
]
ASF GitHub Bot logged work on KNOX-3282:
----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Mar/26 07:25
Start Date: 19/Mar/26 07:25
Worklog Time Spent: 10m
Work Description: smolnar82 opened a new pull request, #1179:
URL: https://github.com/apache/knox/pull/1179
[KNOX-3282](https://issues.apache.org/jira/browse/KNOX-3282) - Logging some
CM discovery errors at `INFO` level
## What changes were proposed in this pull request?
I switched the stack trace level to `INFO` (from `DEBUG`) in case of some
initial CM service discovery actions to make troubleshooting easier.
## How was this patch tested?
Ran unit tests.
## Integration Tests
N/A
## UI changes
N/A
Issue Time Tracking
-------------------
Worklog Id: (was: 1010204)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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)
