cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
Date Fri, 12 Dec 2014 16:48:14 GMT

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

Brandon Williams commented on CASSANDRA-6198:
---------------------------------------------

Hmm, this doesn't compile for me (and I used wiggle to get it to patch):

{noformat}
    [javac] /home/drift/cassandra/src/java/org/apache/cassandra/streaming/ConnectionHandler.java:175:
error: cannot find symbol
    [javac]                 if (peer instanceof Inet6Address)
    [javac]                     ^
    [javac]   symbol:   variable peer
    [javac]   location: class MessageHandler
{noformat}

Not sure what went wrong here, but can you rebase?

> Distinguish streaming traffic at network level
> ----------------------------------------------
>
>                 Key: CASSANDRA-6198
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6198
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: sankalp kohli
>            Assignee: Norman Maurer
>            Priority: Minor
>             Fix For: 2.1.3
>
>         Attachments: 0001-CASSANDRA-6198-Set-IPTOS_THROUGHPUT-on-streaming-con-v2.txt,
0001-CASSANDRA-6198-Set-IPTOS_THROUGHPUT-on-streaming-con.txt
>
>
> It would be nice to have some information in the TCP packet which network teams can inspect
to distinguish between streaming traffic and other organic cassandra traffic. This is very
useful for monitoring WAN traffic. 
> Here are some solutions:
> 1) Use a different port for streaming. 
> 2) Add some IP header. 



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

Mime
View raw message