Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 25 Nov 2014 19:19:13 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12673771.1381785433000.18533.1416943153976@Atlassian.JIRA>
In-Reply-To: <JIRA.12673771.1381785433000@Atlassian.JIRA>
References: <JIRA.12673771.1381785433000@Atlassian.JIRA>
 <JIRA.12673771.1381785433824@arcas>
Subject: [jira] [Updated] (CASSANDRA-6198) Distinguish streaming traffic at
 network level
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-6198:
--------------------------------------
    Reviewer: Philip Thompson  (was: Brandon Williams)

> 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
>         Attachments: 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)