cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Magnusson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8777) Streaming operations should log both endpoint and port associated with the operation
Date Fri, 31 Jul 2015 15:24:05 GMT

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

Ryan Magnusson commented on CASSANDRA-8777:
-------------------------------------------

I would like to take this on, but have some questions to clarify the request. 
The description says that "we currently log the endpoint for a streaming operation", but in
the example provided I only see the planId being shown. I see in some parts of the code we
do log out InetAddress, but it isn't in the example provided.
Is the goal of this task to also add the address to messages for stream operations where it
currently is not shown? 

> Streaming operations should log both endpoint and port associated with the operation
> ------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8777
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8777
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jeremy Hanna
>              Labels: lhf
>             Fix For: 2.1.x
>
>
> Currently we log the endpoint for a streaming operation.  If the port has been overridden,
it would be valuable to know that that setting is getting picked up.  Therefore, when logging
the endpoint address, it would be nice to also log the port it's trying to use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message