cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (CASSANDRA-8457) nio MessagingService
Date Thu, 13 Apr 2017 13:30:42 GMT

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

Jason Brown updated CASSANDRA-8457:
-----------------------------------
    Comment: was deleted

(was: bq. doesn't Netty already have a standard way to deal with that problem of messages
piling up in its queues?

Netty has a high/low water mark mechanism that looks at the number of bytes in the channel
and sends a "writablility changed" event through channel once one of those thresholds has
been reached. I'm currently using that feature to know when we've hit a decent amount of buffered
data before we explicitly call flush.

We could expand this to say "if there's greater than <wildly large> number of bytes
in the channel, drop older messages")

> nio MessagingService
> --------------------
>
>                 Key: CASSANDRA-8457
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8457
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jonathan Ellis
>            Assignee: Jason Brown
>            Priority: Minor
>              Labels: netty, performance
>             Fix For: 4.x
>
>
> Thread-per-peer (actually two each incoming and outbound) is a big contributor to context
switching, especially for larger clusters.  Let's look at switching to nio, possibly via Netty.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message