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 2026/10/22 20:35:00 UTC
[jira] [Commented] (KNOX-3526) Redeploy topologies on gateway-reloadable configuration changes via reloadableListener topology attribute
[ https://issues.apache.org/jira/browse/KNOX-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18130569#comment-18130569 ]
ASF subversion and git services commented on KNOX-3526:
-------------------------------------------------------
Commit e19e63e4faade107cc3f944e41327e3b94e764ed in knox's branch refs/heads/master from hanicz
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=e19e63e4f ]
KNOX-3526: Redeploy topologies with reloadableListener on gateway-rel… (#1466)
* KNOX-3526: Redeploy topologies with reloadableListener on gateway-reloadable.xml changes
* KNOX-3526: Keep notifying listeners in case of exceptions. Admin API now saves the reloadableListener flag.
> Redeploy topologies on gateway-reloadable configuration changes via reloadableListener topology attribute
> ---------------------------------------------------------------------------------------------------------
>
> Key: KNOX-3526
> URL: https://issues.apache.org/jira/browse/KNOX-3526
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 3.0.0
> Reporter: Tamás Hanicz
> Assignee: Tamás Hanicz
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Knox reloads gateway-reloadable.xml at runtime when the file changes, but there is no way for topologies to react to such a change. Topologies that depend on reloadable configuration keep running with the values they were deployed with until they are redeployed manually.
> We need a listener mechanism on gateway-reloadable configuration updates, and a per-topology opt-in that redeploys the topology when the reloadable configuration changes.
> h3. Requirements
> * gateway-reloadable supports registering listeners that are notified when a configuration update is detected.
> * Topologies get a new attribute, reloadableListener, which defaults to false.
> * When reloadableListener is true for a topology and the reloadable configuration changes, that specific topology is redeployed.
> * Topologies with reloadableListener set to false (or not set) are unaffected by reloadable configuration changes.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)