You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "sankalp kohli (JIRA)" <ji...@apache.org> on 2012/08/10 02:05:19 UTC
[jira] [Commented] (CASSANDRA-4521) OutboundTcpConnection could
drop outgoing messages and not log it.
[ https://issues.apache.org/jira/browse/CASSANDRA-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432321#comment-13432321 ]
sankalp kohli commented on CASSANDRA-4521:
------------------------------------------
Please delete this JIRA. Duplicate of https://issues.apache.org/jira/browse/CASSANDRA-4516.
Created because of error in JIRA
> OutboundTcpConnection could drop outgoing messages and not log it.
> -------------------------------------------------------------------
>
> Key: CASSANDRA-4521
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4521
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2
> Environment: trunk
> Reporter: sankalp kohli
> Priority: Minor
> Labels: message
> Original Estimate: 0.1h
> Remaining Estimate: 0.1h
>
> Since there is one connection between two nodes and all writes are handled by single thread, there is a chance that a message gets old enough and is dropped in OutboundTcpConnection. These dropped message does not get logged by MessageService.
> We should definitely log these.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira