[
https://issues.apache.org/jira/browse/DRILL-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022127#comment-17022127
]
Arina Ielchiieva commented on DRILL-7546:
-----------------------------------------
The problem is that current endpoint in stored DrillbitContext before it
changes its status or has assigned httpPort. Before adding status to endpoints
they were immutable and thus everything was ok. I see that most of the
comparison is done in hard / soft distribution but so far looking at the code
current and active endpoints are not mixed, maybe that's why all works ok now
(at least I hope so).
> 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)
