[jira] [Commented] (DRILL-7546) DrillbitContext.getEndpoint state is allways "startup"

["Oleg Zinoviev (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DRILL-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021290#comment-17021290 ] 

Oleg Zinoviev commented on DRILL-7546:
--------------------------------------

Same for httpPort in DrillbitContext:: getEndpoint (allways not set)

> 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 AssignmentCreator. 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)