[
https://issues.apache.org/jira/browse/CASSANDRA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069218#comment-13069218
]
Vijay edited comment on CASSANDRA-1405 at 7/21/11 9:23 PM:
-----------------------------------------------------------
Sorry, had a typo in my original patch... DebuggableThreadPoolExecutor min and
max was the same.... which i fixed in my version but somehow lost it...
was (Author: [email protected]):
Sorry, had a typo in my original patch... DebuggableThreadPoolExecutor min
and max was the same....
> Switch to THsHaServer, redux
> ----------------------------
>
> Key: CASSANDRA-1405
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1405
> Project: Cassandra
> Issue Type: Improvement
> Components: API
> Reporter: Jonathan Ellis
> Assignee: Vijay
> Priority: Minor
> Fix For: 0.8.3
>
> Attachments: 0001-including-validation.patch,
> 0001-log4j-config-change.patch, 0002-commiting-typo-in-DTPE.patch,
> 1405-Thrift-Patch-SVN.patch, libthrift-r1026391.jar, trunk-1405.patch
>
>
> Brian's patch to CASSANDRA-876 suggested using a custom TProcessorFactory
> subclass, overriding getProcessor to reset to a default state when a new
> client connects. It looks like this would allow dropping
> CustomTThreadPoolServer as well as allowing non-thread based servers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
