[
https://issues.apache.org/jira/browse/HDDS-12627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz-wo Sze updated HDDS-12627:
------------------------------
Description:
Found two bugs in NodeStateMap:
# in updateNodeHealthState, it does not pass the opStateExpiryEpochSeconds from
the oldStatus to the newStatus, i.e. the newStatus will always have
opStateExpiryEpochSeconds == 0.
# in filterNodes, when both opState and health are non-null, the matched nodes
must also have opStateExpiryEpochSeconds == 0, i.e. the non-zero
opStateExpiryEpochSeconds won't be matched.
was:
Found two bugs in NodeStateMap:
# in updateNodeHealthState, it does not pass the updateNodeHealthState from
the oldStatus to the newStatus, i.e. the newStatus will always have
opStateExpiryEpochSeconds == 0.
# in filterNodes, when both opState and health are non-null, the matched nodes
must also have opStateExpiryEpochSeconds == 0, i.e. the non-zero
opStateExpiryEpochSeconds won't be matched.
> NodeStateMap may handle opStateExpiryEpochSeconds incorrectly
> -------------------------------------------------------------
>
> Key: HDDS-12627
> URL: https://issues.apache.org/jira/browse/HDDS-12627
> Project: Apache Ozone
> Issue Type: Bug
> Components: SCM
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.1.0
>
>
> Found two bugs in NodeStateMap:
> # in updateNodeHealthState, it does not pass the opStateExpiryEpochSeconds
> from the oldStatus to the newStatus, i.e. the newStatus will always have
> opStateExpiryEpochSeconds == 0.
> # in filterNodes, when both opState and health are non-null, the matched
> nodes must also have opStateExpiryEpochSeconds == 0, i.e. the non-zero
> opStateExpiryEpochSeconds won't be matched.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
