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] [Comment Edited] (CASSANDRA-8777) Streaming operations should log both endpoint and port associated with the operation
Date Mon, 03 Aug 2015 14:25:05 GMT

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

Ryan Magnusson edited comment on CASSANDRA-8777 at 8/3/15 2:24 PM:
-------------------------------------------------------------------

Thanks @Gary Dusbabek.

Is there any reservation from the group with using InetSocketAddress instead of just InetAddress
with Stream operations?


was (Author: ryanmagnusson):
Thanks Gary Dusbabek.

Is there any reservation from the group with using InetSocketAddress instead of just InetAddress
with Stream operations?

> 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