cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CASSANDRA-2858) make request dropping more accurate
Date Wed, 26 Sep 2012 20:37:08 GMT

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

Yuki Morishita reopened CASSANDRA-2858:
---------------------------------------


I think this is not working as expected.
Truncate hangs on two node cluster using 1.2.0-beta1 binary because truncate response gets
dropped every time(and this is why CliTest on trunk is failing today).

I think casting long System.currentTimeMillis to int is fragile, and that's causing this line

https://github.com/apache/cassandra/blob/cassandra-1.2.0-beta1/src/java/org/apache/cassandra/net/MessageDeliveryTask.java#L43

always evaluates to true.
When I tried, System.currentTimeMillis was like 1348691631776, but currentTime there was like
71900832.
                
> make request dropping more accurate
> -----------------------------------
>
>                 Key: CASSANDRA-2858
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2858
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Ryan King
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.2.0 beta 1
>
>         Attachments: 2858.txt, 2858-v2.txt, 2858-v3.txt
>
>
> Based on the discussion in CASSANDRA-2819, we can make the bookkeeping for request times
more accurate.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message