cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1057) Login information stored in threads may be reused.
Date Fri, 28 May 2010 18:10:36 GMT


Jonathan Ellis commented on CASSANDRA-1057:

It would be nice to have a workaround in Cassandra 0.6.3.  Can you submit a patch with you
TTPS modification?

> Login information stored in threads may be reused.
> --------------------------------------------------
>                 Key: CASSANDRA-1057
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6
>            Reporter: Kenny
>            Priority: Minor
>             Fix For: 0.6.3
> CassandraServer stores the login information in a ThreadLocal<AccessLevel>.
> CassandraDaemon starts the server with 64 threads. When the first 64 clients connect
they should get their own thread, but after that threads will be reused.
> In a quick test I created a Server with 5 threads, and a ThreadLocal<Integer>,
and the value is seen by new clients connecting.
> Thrift doesn't destroy the threads when a client disconnects. Maybe an option in Thrift
would make more sense to make this method usable.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message