[
https://issues.apache.org/jira/browse/NIFI-14785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010421#comment-18010421
]
ASF subversion and git services commented on NIFI-14785:
--------------------------------------------------------
Commit 0313fa1ffcb50188e1766374fac55a63ee6bbf3f in nifi's branch
refs/heads/dependabot/npm_and_yarn/nifi-frontend/src/main/frontend/axios-1.11.0
from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0313fa1ffc ]
NIFI-14785 Handle exception or null responses from fetching node statuses and
fall back to local state
Signed-off-by: Pierre Villard <[email protected]>
This closes #10132.
> cluster-status command can be broken while upgrading a cluster
> --------------------------------------------------------------
>
> Key: NIFI-14785
> URL: https://issues.apache.org/jira/browse/NIFI-14785
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Fix For: 2.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In NIFI-14758 we added a new message type to the cluster protocol for
> fetching node statuses from the cluster coordinator and `bin/nifi.sh
> cluster-status` now calls this.
> This creates an issue if this command is called during a rolling upgrade
> because the newly upgrade node will make this call to the coordinator, but
> the coordinator doesn't support this message type yet.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
