[
https://issues.apache.org/jira/browse/KNOX-3194?focusedWorklogId=984211&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-984211
]
ASF GitHub Bot logged work on KNOX-3194:
----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Sep/25 20:17
Start Date: 23/Sep/25 20:17
Worklog Time Spent: 10m
Work Description: smolnar82 opened a new pull request, #1088:
URL: https://github.com/apache/knox/pull/1088
## What changes were proposed in this pull request?
As described in KNOX-3194, the cluster-level `RollingRestart` and
`RestartWaitingForStalenessSuccess` should trigger a full service discovery.
## How was this patch tested?
Updated and executed existing unit tests.
Manual testing on a real cluster with HMS (I'll add details later...)
Issue Time Tracking
-------------------
Worklog Id: (was: 984211)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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)
