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/04/27 14:59:00 UTC

[jira] [Commented] (KNOX-2351) Prevent the CM configuration monitor from being suspended

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

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

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

KNOX-2351 - Catching any errors while monitoring CM configuration changes (#324)



> Prevent the CM configuration monitor from being suspended
> ---------------------------------------------------------
>
>                 Key: KNOX-2351
>                 URL: https://issues.apache.org/jira/browse/KNOX-2351
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: cm-discovery
>    Affects Versions: 1.4.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 1.5.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> While debugging the root cause of KNOX-2350, I found out that if there was any uncaught issue while monitoring CM configuration in {{PollingConfigurationAnalyzer}} the entire thread became suspended and there was no easy way to figure out what the problem was.
> This needs to be fixed.



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