You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (Jira)" <ji...@apache.org> on 2021/09/27 08:31:00 UTC
[jira] [Updated] (CASSANDRA-16997) Handle timestamp wraparound for
internode messages
[ https://issues.apache.org/jira/browse/CASSANDRA-16997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson updated CASSANDRA-16997:
----------------------------------------
Bug Category: Parent values: Availability(12983)Level 1 values: Response Crash(12991)
Complexity: Normal
Component/s: Messaging/Internode
Discovered By: Adhoc Test
Fix Version/s: 4.x
4.0.x
Severity: Normal
Status: Open (was: Triage Needed)
> Handle timestamp wraparound for internode messages
> --------------------------------------------------
>
> Key: CASSANDRA-16997
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16997
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 4.0.x, 4.x
>
>
> In internode messaging we send the lower 4 bytes of the timestamp and then correct on receiving side if the local time has wrapped (every 50 days), but we currently don't correct the time if the sending side wrapped before us.
> This can cause us to use the wrong timestamp for the message and if the local System.nanoTime is < 50 days, we get a negative creation time which causes an AssertionError in MonitorableImpl
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org