[
https://issues.apache.org/jira/browse/CASSANDRA-13205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15860341#comment-15860341
]
Blake Eggleston commented on CASSANDRA-13205:
---------------------------------------------
There are also a couple of log messages
[here|https://github.com/bdeggleston/cassandra/blob/af3fe39dcabd9ef77a00309ce6741268423206df/src/java/org/apache/cassandra/hints/HintsReader.java#L229-L229]
and
[here|https://github.com/bdeggleston/cassandra/blob/af3fe39dcabd9ef77a00309ce6741268423206df/src/java/org/apache/cassandra/hints/HintsReader.java#L242-L242]
in HintsReader that refer to hostId, and not endpoint. Also, while you're in
the area, there's a warning in the 3.0 version of the HintVerbHandler that
intends to log the table id
[here|https://github.com/jeffjirsa/cassandra/blob/033596b8174493d0840969fa15624c6c1426a0fc/src/java/org/apache/cassandra/hints/HintVerbHandler.java#L71]
but does not.
> Hint related logging should include the IP address of the destination in
> addition to host ID
> --------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-13205
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13205
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jeff Jirsa
> Assignee: Jeff Jirsa
> Priority: Trivial
> Fix For: 3.0.x
>
>
> After the hint rewrite in 3.0, many of the hint related logs now use hostId
> UUIDs rather than endpoint addresses. This complicates debugging
> unnecessarily. We should include both.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
