[
https://issues.apache.org/jira/browse/ASTERIXDB-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724736#comment-17724736
]
ASF subversion and git services commented on ASTERIXDB-3186:
------------------------------------------------------------
Commit d345cdcdee0f14302b94eeb0b8cb300cd6570586 in asterixdb's branch
refs/heads/master from Murtadha Makki Al Hubail
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=d345cdcdee ]
[ASTERIXDB-3186][HYR] Resolve NC address on CC for heartbeat acks
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- Ensure that the nc address is resolved on the CC when
sending a negative heartbeat ack.
Change-Id: I4ed0f1dda6508ab502e1eb9a38d033da26de6465
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17539
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Ali Alsuliman <[email protected]>
> Invalid NC address used on negative heartbeat ack
> -------------------------------------------------
>
> Key: ASTERIXDB-3186
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3186
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: HYR - Hyracks
> Affects Versions: 0.9.8
> Reporter: Murtadha Makki Al Hubail
> Assignee: Murtadha Makki Al Hubail
> Priority: Major
> Labels: triaged
> Fix For: 0.9.9
>
>
> In NodeHeartbeatWork, the CC currently attempts to send negative heartbeat
> ack using the ncAddress that was received by the NC. Since this address was
> resolved in the NC then sent to the CC, the CC could potentially send the ack
> to a wrong NC. We need to resolve the ncAddress on the CC in this case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
