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

Abe Ratnofsky commented on CASSANDRA-20317:
-------------------------------------------

I'd recommend looking into custom outbound connection initiators, which set 
socket options already: 
[https://github.com/apache/cassandra/blob/511bd203144a71bf0a72876a393d186a9778407e/src/java/org/apache/cassandra/net/OutboundConnectionInitiator.java#L193]

You'd use .option(ChannelOption.IP_TOS, tos) to set those bits in 
OutboundConnectionInitiator. I would recommend making this an optional 
configuration as part of OutboundConnectionSettings.

You might have to experiment with padding, since different systems permit 
different masks over the TOS bits in the IP header.

> Set traffic classes on network traffic
> --------------------------------------
>
>                 Key: CASSANDRA-20317
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20317
>             Project: Apache Cassandra
>          Issue Type: New Feature
>            Reporter: Tommy Stendahl
>            Assignee: Tommy Stendahl
>            Priority: Normal
>
> I would like to add the possibility to set traffic classes on network traffic 
> from Cassandra. I was thinking of one value for traffic from the native port 
> and different values for inbound and outbound internode traffic. To configure 
> this in the yaml file I like to add something like this:
> {quote} # Set traffic classes in IP packages
> #
>  # Traffic classes can be used to separate traffic in a network into 
> individual flows
>  # and queue, police and shape them differently.
>  # traffic_classes:
>   # enabled: false
>   # native_tc: 0
>   # internode_outbound_tc: 0
>   # internode_inbound_tc: 0{quote}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to