[
https://issues.apache.org/jira/browse/KNOX-2368?focusedWorklogId=429224&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-429224
]
ASF GitHub Bot logged work on KNOX-2368:
----------------------------------------
Author: ASF GitHub Bot
Created on: 30/Apr/20 19:42
Start Date: 30/Apr/20 19:42
Worklog Time Spent: 10m
Work Description: pzampino opened a new pull request #333:
URL: https://github.com/apache/knox/pull/333
… Restart Events
## What changes were proposed in this pull request?
Added cluster config monitor support for rolling restarts of individual
services and complete clusters. This also fixes a previously-introduced defect
whereby the monitor would recognize relevant events whose status is STARTED,
which would result in false-positive inclusion of events that would trigger
configuration analysis. All the relevant commands have status value of
SUCCEEDED once they've successfully completed. Since the "Rolling Restart"
option is disabled in the CM cluster against which I've tested, the
implementation and associated test of that behavior is entirely based on log
content that exposed the need for this PR.
## How was this patch tested?
Refactored and augmented PollingConfigurationAnalyzerTest, and manually
tested all the supported scenarios (except rolling CLUSTER restart).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 429224)
Remaining Estimate: 0h
Time Spent: 10m
> CM Cluster Configuration Monitor Does Not Support Rolling Restart Events
> ------------------------------------------------------------------------
>
> Key: KNOX-2368
> URL: https://issues.apache.org/jira/browse/KNOX-2368
> Project: Apache Knox
> Issue Type: Bug
> Components: cm-discovery
> Affects Versions: 1.4.0
> Reporter: Philip Zampino
> Assignee: Philip Zampino
> Priority: Major
> Fix For: 1.5.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The ClouderaManager cluster configuration monitor does not currently check
> for rolling restarts of individual services or entire clusters. While it's
> unlikely for an admin to effect port-related configuration changes as part of
> a rolling restart, the monitor should still be able to respond to such a
> scenario.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
