[
https://issues.apache.org/jira/browse/IMPALA-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516460#comment-16516460
]
Dan Hecht commented on IMPALA-7183:
-----------------------------------
Is there an easy way to determine which host was the sender at this point? I
think that's only known by the coordinator object, but that's gone. I think
it's possible once we switch the RPC to KRPC however since the KRPC layer can
tell us.
> We should print the sender name when logging a report for an unknown status
> report on the coordinatior
> ------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-7183
> URL: https://issues.apache.org/jira/browse/IMPALA-7183
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend, Distributed Exec
> Affects Versions: Impala 2.13.0, Impala 3.1.0
> Reporter: Lars Volker
> Priority: Critical
> Labels: ramp-up
>
> We should print the sender name when logging a report for an unknown status
> report on the coordinatior in
> [impala-server.cc:1229|https://github.com/apache/impala/blob/e7d5a25a4516337ef651983b1d945abf06c3a831/be/src/service/impala-server.cc#L1229].
> That will help identify backends with stuck fragment instances who fail to
> get cancelled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
