[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[
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)
[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[ https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237726#comment-14237726 ] Norman Maurer commented on CASSANDRA-6198: -- [~brandon.williams] sorry for the delay, just addressed your comment and uploaded a new version of the patch with the change included. > 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)
[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[ https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226593#comment-14226593 ] Brandon Williams commented on CASSANDRA-6198: - Please do, and I will perform a final review and commit after the holiday. > 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.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)
[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[ https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226587#comment-14226587 ] Norman Maurer commented on CASSANDRA-6198: -- Agree Boolean.getBoolean(...) would be better. Should I adjust the patch ? > 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.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)
[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[ https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225260#comment-14225260 ] Brandon Williams commented on CASSANDRA-6198: - Why not use Boolean.getBoolean here? > 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.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)
[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[ https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225057#comment-14225057 ] Jonathan Ellis commented on CASSANDRA-6198: --- [~philipthompson to review] > 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)
[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[ https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220968#comment-14220968 ] Norman Maurer commented on CASSANDRA-6198: -- Please review... > 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)
[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[ https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046225#comment-14046225 ] sankalp kohli commented on CASSANDRA-6198: -- I have not heard back after creating a ticket. Closing since we no longer need it as well. > 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: sankalp kohli >Priority: Minor > > 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.2#6252)
[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[ https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832117#comment-13832117 ] sankalp kohli commented on CASSANDRA-6198: -- As per javadoc in http://docs.oracle.com/javase/7/docs/api/java/nio/channels/SocketChannel.html IP_TOS is not listed. So I am not sure whether it is a bug. > 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: sankalp kohli >Priority: Minor > > 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.1#6144)
[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[
https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832051#comment-13832051
]
Jonathan Ellis commented on CASSANDRA-6198:
---
Hmm. At the very least I would expect
{{channel.setOption(StandardSocketOptions.IP_TOS, 8);}} to work. Suggest
filing a bug at https://bugs.openjdk.java.net/secure/Dashboard.jspa and see
what they come back with.
> 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: sankalp kohli
>Priority: Minor
>
> 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.1#6144)
[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[
https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832045#comment-13832045
]
sankalp kohli commented on CASSANDRA-6198:
--
I am having trouble setting the value on the socket. Since we create the socket
from SocketChannel, I am not able to set the TOS.
http://docs.oracle.com/javase/7/docs/api/java/nio/channels/SocketChannel.html
Here is a sample code I tried running on OSX and Linux in Java 1.7. The IP
x.y.z pointed to a test cassandra instance running 2.0.2
Socket socket = SocketChannel.open(new InetSocketAddress("x.y.z",
7000)).socket();
socket.setTrafficClass(8);
System.out.println(socket.getTrafficClass());// WIll print 0
SocketChannel channel = SocketChannel.open(new
InetSocketAddress("x.y.z", 7000));
channel.setOption(StandardSocketOptions.IP_TOS, 8);
System.out.println(channel.getOption(StandardSocketOptions.IP_TOS));//
WIll print 0
System.out.println(channel.socket().getTrafficClass());// WIll print 0
channel.socket().setTrafficClass(8);
System.out.println(channel.socket().getTrafficClass()); // WIll print 0
//This will work and prints 8
Socket socket1 = new Socket("x.y.z", 7000);
socket1.setTrafficClass(8);
System.out.println(socket1.getTrafficClass()); // WIll print 8
> 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: sankalp kohli
>Priority: Minor
>
> 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.1#6144)
[jira] [Commented] (CASSANDRA-6198) Distinguish streaming traffic at network level
[ https://issues.apache.org/jira/browse/CASSANDRA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794524#comment-13794524 ] Brandon Williams commented on CASSANDRA-6198: - One thing we could do is socket.setTrafficClass to IPTOS_THROUGHPUT on outbound streaming connections. I'm not sure how many routers respect the TOS field, but if they do this setting seems fairly appropriate anyway. > 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 >Priority: Minor > > 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.1#6144)
