cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Deng (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-10901) Per client TCP/IP connection quota
Date Thu, 17 Dec 2015 22:38:46 GMT
Wei Deng created CASSANDRA-10901:
------------------------------------

             Summary: Per client TCP/IP connection quota
                 Key: CASSANDRA-10901
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10901
             Project: Cassandra
          Issue Type: New Feature
          Components: Coordination
            Reporter: Wei Deng


Now that we started working on CASSANDRA-9318, could we also consider pushing it one step
further to accommodate some per user/session quota? This will be useful in a multi-tenant
Cassandra deployment.

My intention is to keep it simple, i.e. only enforcing quota at the node level, with protocol
v3+ most likely you only need one TCP/IP connection (to accommodate 32K stream ids) so just
enforcing some sort of in-flight request limit based on each TCP/IP connection looks good
enough for me; if any client would ever need to add another TCP/IP connection (as they run
out of the 32k stream ids), there should be no limit/quota existing on them already before
that's allowed (the assumption here is that each client is connected to the cluster using
only one Cassandra user).



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

Mime
View raw message