You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/01/31 16:04:00 UTC

[jira] [Commented] (KNOX-2206) Cloudera Manager - Service Discovery - log exclusion of a service due to configuration issues

    [ https://issues.apache.org/jira/browse/KNOX-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027615#comment-17027615 ] 

ASF subversion and git services commented on KNOX-2206:
-------------------------------------------------------

Commit 278de057af78c59781d9ac10681d0f6ae8c05fa6 in knox's branch refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=278de05 ]

KNOX-2206 - Log exclusion of a discovered service due to configuration issues (#248)




> Cloudera Manager - Service Discovery - log exclusion of a service due to configuration issues
> ---------------------------------------------------------------------------------------------
>
>                 Key: KNOX-2206
>                 URL: https://issues.apache.org/jira/browse/KNOX-2206
>             Project: Apache Knox
>          Issue Type: New Feature
>          Components: cm-discovery
>    Affects Versions: 1.4.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 1.4.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> If a service does not get discovered due to a missing/wrong configuration there is no any trace to find out if that happened. At a minimum, a WARN level message should be added in the logs saying something similar to 'service X is excluded because configuration Y does not exists or incorrect'



--
This message was sent by Atlassian Jira
(v8.3.4#803005)