[
https://issues.apache.org/jira/browse/DRILL-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Zinoviev updated DRILL-7546:
---------------------------------
Summary: DrillbitContext.getEndpoint state is allways "startup" (was:
DrillbitContext.getCurrentEndpoint state is allways "startup")
> DrillbitContext.getEndpoint state is allways "startup"
> ------------------------------------------------------
>
> Key: DRILL-7546
> URL: https://issues.apache.org/jira/browse/DRILL-7546
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.16.0
> Reporter: Oleg Zinoviev
> Priority: Major
>
> For now DrillbitContext:: getEndpoint::getState always returns STARTUP. Since
> CoordinationProtos.DrillbitEndpoint is actively used in comparisons on equals
> or as a key in hash map (e.g. in AssignmentCreator). this can lead to
> situations where the comparison for the current node returns false if the
> node information obtained from the coordinator and from
> DrillbitContext::getEndpoint is compared.
> I think I see this situation in Assignment Creator. Could you check this
> behavior? Unfortunately, I don't understand how to write a test that
> demonstrates this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
