[
https://issues.apache.org/jira/browse/KNOX-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-3194:
--------------------------------
Status: Patch Available (was: In Progress)
> CM service discovery issues in case of cluster rolling restart/wait for
> staleness success
> -----------------------------------------------------------------------------------------
>
> Key: KNOX-3194
> URL: https://issues.apache.org/jira/browse/KNOX-3194
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 2.1.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> KNOX-2410 added the ability to handle CM's
> {{RestartWaitingForStalenessSuccess}} command the same way as we did for
> cluster-level rolling restart.
> Then KNOX-2907 introduced a bug and invalidated those cases.
> As a result, Knox doesn't consider the {{RollingRestart}} and
> {{RestartWaitingForStalenessSuccess}} commands, when triggered by the CM
> server (i.e. rolling restart doesn't happen on the role level).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
