[
https://issues.apache.org/jira/browse/KNOX-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18022354#comment-18022354
]
ASF subversion and git services commented on KNOX-3194:
-------------------------------------------------------
Commit 435b91482a305a3bbfc9bc0555dda7faa06fd2f3 in knox's branch
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=435b91482 ]
KNOX-3194 - CM-initiated rolling restart and waitForStalenessSuccess commands
should trigger a discovery round (#1088)
> 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: 0.5h
> 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 is
> wrong. When such an event is received (only when the status is
> {{SUCCEEDED}}), CM discovery should happen.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
