[jira] [Commented] (KNOX-2994) Postpone CM configuration change monitoring until the Knox GW is up

2024-02-27 Thread ASF subversion and git services (Jira) 


[ 
https://issues.apache.org/jira/browse/KNOX-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821097#comment-17821097
 ] 

ASF subversion and git services commented on KNOX-2994:
---

Commit bb6719f3cad33cc89c990a2ab5bc61756c497d4f in knox's branch 
refs/heads/dependabot/npm_and_yarn/gateway-admin-ui/http-cache-semantics-4.1.1 
from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=bb6719f3c ]

KNOX-2994 - PollingConfigurationAnalyzer starts after the Knox GW is up and 
running (#831)



> Postpone CM configuration change monitoring until the Knox GW is up
> ---
>
> Key: KNOX-2994
> URL: https://issues.apache.org/jira/browse/KNOX-2994
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: cm-discovery, Server
>Affects Versions: 1.5.0, 2.0.0, 1.6.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Fix For: 2.1.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> As of now, Knox starts CM configuration change monitoring right away it 
> starts the {{{}DefaultClusterConfigurationMonitorService{}}}. This action 
> will trigger the {{PollingConfigurationAnalyzer}} even when descriptors with 
> possible service discovery settings are not even initialized.
> My suggestion is to take advantage of the recently introduced 
> {{GatewayStatusService}} and set the {{isActive}} flag to true based on the 
> result of 
> {{{}org.apache.knox.gateway.services.topology.impl.GatewayStatusService.status(){}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (KNOX-2994) Postpone CM configuration change monitoring until the Knox GW is up

2024-01-03 Thread ASF subversion and git services (Jira) 


[ 
https://issues.apache.org/jira/browse/KNOX-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17802501#comment-17802501
 ] 

ASF subversion and git services commented on KNOX-2994:
---

Commit bb6719f3cad33cc89c990a2ab5bc61756c497d4f in knox's branch 
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=bb6719f3c ]

KNOX-2994 - PollingConfigurationAnalyzer starts after the Knox GW is up and 
running (#831)



> Postpone CM configuration change monitoring until the Knox GW is up
> ---
>
> Key: KNOX-2994
> URL: https://issues.apache.org/jira/browse/KNOX-2994
> Project: Apache Knox
>  Issue Type: Improvement
>  Components: cm-discovery, Server
>Affects Versions: 1.5.0, 2.0.0, 1.6.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Fix For: 2.1.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> As of now, Knox starts CM configuration change monitoring right away it 
> starts the {{{}DefaultClusterConfigurationMonitorService{}}}. This action 
> will trigger the {{PollingConfigurationAnalyzer}} even when descriptors with 
> possible service discovery settings are not even initialized.
> My suggestion is to take advantage of the recently introduced 
> {{GatewayStatusService}} and set the {{isActive}} flag to true based on the 
> result of 
> {{{}org.apache.knox.gateway.services.topology.impl.GatewayStatusService.status(){}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)