[
https://issues.apache.org/jira/browse/KNOX-2944?focusedWorklogId=872465&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-872465
]
ASF GitHub Bot logged work on KNOX-2944:
----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Jul/23 08:59
Start Date: 24/Jul/23 08:59
Worklog Time Spent: 10m
Work Description: smolnar82 opened a new pull request, #781:
URL: https://github.com/apache/knox/pull/781
## What changes were proposed in this pull request?
Ensure that Impala Daemon's `specialization` role config is stored so that
CM service discovery can detect changes in that property.
## How was this patch tested?
Tested in a real CM-deployed cluster and updated JUnit tests.
Issue Time Tracking
-------------------
Worklog Id: (was: 872465)
Remaining Estimate: 0h
Time Spent: 10m
> Knox cluster monitoring feature does not check on "impalad_specialization" CM
> config
> ------------------------------------------------------------------------------------
>
> Key: KNOX-2944
> URL: https://issues.apache.org/jira/browse/KNOX-2944
> Project: Apache Knox
> Issue Type: Bug
> Components: cm-discovery
> Affects Versions: 2.0.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Critical
> Fix For: 2.1.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *Steps to reproduce:*
> # Go to {{impalad}} configuration in host1 in a CM-deployed cluster
> # Update the "{{{}impalad_specialization{}}}" {color:#172b4d}to executor
> only and restart {{impalad}} role{color}
> # {color:#172b4d}Wait for 1 min for the relevant Knox topology to update the
> Impala service API endpoint URLs{color}
> {color:#172b4d}*Issue:*{color}
> Updating impalad_specialization CM config should also be monitored by Knox
> and the topologies should have been redeployed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
